| Author |
 Topic  |
|
|
krlasski
Germany
11 Posts |
 Posted - 03/12/2013 : 05:59:39 AM
|
Origin Ver. and Service Release (Select Help-->About Origin):8.6SR2; 9.0SR1
Operating System: Win7
Hello,
I have a problem with transfering a custom toolbar within Origin. I have a custom-made toolbar involving a few short Origin C scripts for data import stuff, which I would like to share between different computers and different users. So I have exported the toolbar on the source computer into an OPX file.
I also managed to install it successfully into a newer Origin installation on the same computer. However, it doesn't import properly into an Origin installation on another computer. It produced an .xml-file in the "User Files" directory, but the toolbar didn't appear. The behaviour is the same for Origin 8.6 as well as for Origin 9.
One obvious difference between the two systems is the username I'm working under. My suspicion is that Origin tries to extract the files into a directory named like the one on the source computer (which doesn't exist, as the username is different). (I could the target path including the username on the source computer visible in the package manager dialog)
Anyway, my goal is to transfer the toolbar in its entirety to other systems. Is there any way to either correct the "wrong" path in the .OPX file or lead the program into nevertheless using the right path? (Using the same username on all systems is not an option)
Thanks in advance for your help!
Best regards
Kristian Lass
|
|
|
matthew@originlab.com
73 Posts |
Posted - 03/13/2013 : 10:24:26 AM
|
Hi,
Im not sure I entirely understand your situation. You mentioned that you built a custom toolbar that will be used for importing data. However, I wasnt clear if you were saying that the toolbar wasnt installing correctly on another computer, of if the toolbar was installed properly on another machine but wont function correctly when you try to use it to import data. For now Im going to assume you are having difficulty getting the custom toolbar to install and appear in Origin on another computer.
I have a couple other questions that will help me understand your situation:
Did you create the toolbar using the Package Manager, or did you go to View > Toolbars, and create a new Button Group? Do all your source files for the toolbar exist in the same location? Do the C-scripts contain any hard coded paths that wouldnt function properly on another machine?
Also, you mentioned that you installed the toolbar on the 2nd computer, but that it didnt appear. How did you install the toolbar?
Matthew
OriginLab |
 |
|
|
krlasski
Germany
11 Posts |
Posted - 03/18/2013 : 04:55:22 AM
|
Hello,
quote:
Originally posted by matthew@originlab.com
However, I wasnt clear if you were saying that the toolbar wasnt installing correctly on another computer, of if the toolbar
The problem is that the toolbar isn't installing correctly (it doesn't appear at all on the destination computer).
quote:
I have a couple other questions that will help me understand your situation:
Did you create the toolbar using the Package Manager, or did you go to View > Toolbars, and create a new Button Group? Do all your source files for the toolbar exist in the same location? Do the C-scripts contain any hard coded paths that wouldnt function properly on another machine?
Originally, the toolbar was created by creating a new button group. The C script files for the toolbar reside in the same directory (that is, in my case, Documents\Originlab\90\User files (I am using the German version, so the wording might differ a bit)). And the scripts do not contain any hard-coded paths.
quote:
Also, you mentioned that you installed the toolbar on the 2nd computer, but that it didnt appear. How did you install the toolbar?
On the first computer I exported via the "Export" button from the "customize toolbars" dialog (German menu entry: "Ansicht/Symbolleisten"). On the second computer I tried to install it by dragging it into the empty Origin window.
Sorry for not supplying the necessary information at once.
Thanks a lot!
Best regards
Kristian
|
|
|
|
matthew@originlab.com
73 Posts |
Posted - 03/18/2013 : 3:20:15 PM
|
Hi Kristian,
Thank you for the detailed reply. Your installation procedure seems like it should be working, so I'd like to ask just a couple more questions.
When you created the .OPX with Customize Toolbars dialog, were you sure to include the other scripts in the package in addition to the default files.
Also, just a clarifying question, in the original post you mentioned when you created the .OPX it actually created a .XML file in the user files folder, are you sure that wasn't the .OPX file, sometimes Windows will list a .OPX file as an "Origin XML Package"
I will keep thinking about what the problem could be, but if you would be willing, you could email your .OPX file to tech@originlab.com and we use it to identify the problem.
Matthew
OriginLab |
|
|
|
krlasski
Germany
11 Posts |
Posted - 03/19/2013 : 09:48:26 AM
|
Dear Matthew,
quote:
When you created the .OPX with Customize Toolbars dialog, were you sure to include the other scripts in the package in addition to the default files.[quote]
Actually, when hitting the "Export" button in question I don't any way to select further files. Did I do it from the wrong dialog?
[quote]Also, just a clarifying question, in the original post you mentioned when you created the .OPX it actually created a .XML file in the user files folder, are you sure that wasn't the .OPX file, sometimes Windows will list a .OPX file as an "Origin XML Package"
I did doublecheck: The file in question possesses the ending ".xml". To give a more complete answer: Its full name is OPXList.xml.
Thanks again for your help!
Best wishes
Kristian
|
|
|
|
matthew@originlab.com
73 Posts |
Posted - 03/19/2013 : 11:00:13 AM
|
Hi Kristian,
So did you try to install that .xml file on the second computer, or was there a .opx file generated in addition to the .xml file?
Matthew
OriginLab |
|
|
|
krlasski
Germany
11 Posts |
Posted - 03/21/2013 : 05:39:53 AM
|
Dear Matthew,
the reply that your colleague sent me via e-mail actually did the trick and solved the issue:
The problem was that the "Customize Toolbar" dialog contains two "Export" buttons which produce different packages: One on the tab labeled (in German) "Symbolleisten" (toolbars), and one on the tab "Befehle" (commands, probably "Button Groups" in the English version). The "Export" button on the "toolbars" tab led straight to an output filename dialog without further choices what to export; hence I assumed that the program would take care of the rest (in fact the package obviously didn't contain much). I didn't realize that the Export button on the other tab produced a different result (that did work indeed).
Thanks for your help!
Best regards
Kristian
|
|
|
| |
Topic |
|
|
|
Origin Toolbar Transfer (8.6, 9.0)