| T O P I C R E V I E W |
| jmb22 |
Posted - 09/26/2004 : 3:23:19 PM Origin Version (Select Help-->About Origin): 7 Operating System: WinXp
Here is what I want to do:
I have three files: J01A, J01B, and J01C (2 levels of index: number (01, 02, 03, 04, ....), and letter (A, B, C))
1)When, I drag and drop the file J01A, I want a subfolder named J01 to be created (removing the second level of index), and the worksheet J01A to be moved into it. Then, when I import J01B, or/and J01C , the corresponding wks are directly moved into J01 subfolder. The code has to be flexible enough so when I drag and drop files J02A, J03C or J04B, the subfolders J02, J03 and J04 are respectively created.
2) The second objective is to copy 2 columns from J01A and J01C to J01B and do calculations between those new columns and the inherent J01B columns. I know how to do calculations between columns of the same worksheet, but I don't know how to copy columns from one wks to another.
That's it! I appreciate your help.
PS: I was trying the new version of Origin (7.5), and the great Import Wizard Option. One thing, I didn't work out, is how to reopen a filter (oif) that was generated for another project. To be more clear, let's say I have created an import filter for *.dat files with some additional labtalk codes (option in the last window of the Import Wizard). If I want to make change to the labtalk code in that filter, I have to start the Wizard from the beginning and change the Labtalk code. I tried to edit the filter with Notepad, but it is not clear where is stored the extra labtalk code . Is there a way to edit the filter and change the labtalk code without having to start the import wizard from the beginning. |
| 1 L A T E S T R E P L I E S (Newest First) |
| easwar |
Posted - 09/26/2004 : 9:58:47 PM Hello,
To answer your last question on import filter: The filter is saved as an XML file and so could be edited in an application such as NotePad - the LabTalk code is saved under a branch called <PostImportScript>. However, this is probably not the best thing to do. If you want to repeatedly edit the script, I suggest first placing the script in an OGS script file under some section name, and then you can just include a run.section(filename, section name); command in place of your entire script, in the import wizard window. Then you can keep editing the script directly with the OGS file using Code Builder until you get things working. Then you can even cut and paste the final code in the import wizard interface one last time, and then discard the OGS file.
Now, regarding questions 1 and 2, you may find it more flexible and easy to perform these tasks if you program in Origin C. There is access to Project Explorer from Origin C. You can also call import functions and refer to saved import filter .OIF files to perform the import programmatically. Manipulation of datasets is easy as well.
For help with Origin C coding, please post in the Origin C forum.
Easwar OriginLab
|
|
|