| T O P I C R E V I E W |
| reoddai |
Posted - 01/07/2005 : 12:13:17 PM
Origin Version (Select Help-->About Origin):
Operating System: Origin 7SR2 V7.0383
I've designed a script called test.ogs:
[Main]
type -b "Oh yah";
In Origin, I've assgined one of the "User Defined" buttons to this OGS and here is the OUTtn.ini file:
;User defined toolbar information.
[Common]
GroupName=User Defined
BitmapFile=User_Test.bmp
ButtonCount=7
[CustomButton1]
Id=48150
Image=0
FileName=test.ogs
SectionName=Main
ArgumentList=
ContextWindow=2
TemplateName=
Worksheet=1
Graph=1
Matrix=1
Excel=1
Layout=1
ToolTip=
StatusBarMsg=
Variable=
I click and I click (yes I know, but frustration has set in after the 20th check) and the box never shows up.
Any help with this would be really appreciated. Even if its so simple an answer that I have to kick myslf.
Thanx in Advance,
Reod Dai |
| 5 L A T E S T R E P L I E S (Newest First) |
| Mike Buess |
Posted - 01/10/2005 : 11:35:22 AM
Hi Reod,
Most error messages are clearly marked... "Error: something" or "Command Error: something". I wouldn't worry about something as cryptic as Øõ".
Mike Buess
Origin WebRing Member
Edited by - Mike Buess on 01/10/2005 11:36:10 AM |
| reoddai |
Posted - 01/10/2005 : 10:05:39 AM
Okay, I see what was happening.
I originally wrote up this problem because I couldn't get my button to work with a lengthy program that I had written. So I created the test.ogs file to quickly test.
So, I went back to the User Toolbar and changed the information there, thus the new OUTtn.ini file. However, the details of the old button I had created were not updated and retained the old information.
Thank you for your help!
You mentioned something about errors? I tried running the old obsolete button and got this:
Øõ"
Is there a place I can go to find out what this error translates to?
Reod Dai |
| Mike Buess |
Posted - 01/07/2005 : 2:58:01 PM
I can only suggest a few quick tests...
1. Open the script window and click your button while pressing the Shift and Control keys. This should appear in the script window...
Menu id=48150
run.section(C:\Program Files\OriginLab\OriginPro7\test.ogs,Main)
2. Type echo=1 and press enter. Then click your button and look for an error message in the script window. (Set echo=0 to turn off error reporting when you're done.)
3. While you have the script window open you might as well make sure the type -b "Oh yah" command works from there.
I don't know what to expect at this point so I'll just wait for your response.
Mike Buess
Origin WebRing Member |
| reoddai |
Posted - 01/07/2005 : 2:24:51 PM
Thanks for the quick reply. I went to check out the solution you proposed and this is where the settings of the button refer to:
C:\Program Files\OriginLab\OriginPro7\test.ogs
I doubled checked that the file is in fact in this directory and yes, it is.
I'm open to any other suggetsions and appreciate all the help!
Edited by - reoddai on 01/07/2005 2:25:51 PM |
| Mike Buess |
Posted - 01/07/2005 : 1:03:27 PM
Your script and button settings are fine so the only possibility I can think of is that Origin can't find the script file. Open the button's settings (View->Toolbars->Button Groups tab, find User Defined group, select the button and click Settings) and examine the path in the File Name box. Once or twice I've seen it corrupted... for example, C:\Origin\test.ogs becomes C:\Origin\C:\Origin\test.ogs. If your script file is in the Origin program folder you can fix it by replacing the full file path\name with just the file name... test.ogs.
Hope that helps.
Mike Buess
Origin WebRing Member |
