I would like an option for Adopt All to exclude procedure files that were loaded automatically because they are in the Igor Procedures folder. Presently if I use Adopt All in an experiment, then open that experiment again later on the same machine, I get a mess as all the procedures in my Igor Procedures folder duplicate ones that are already contained in the experiment. It's especially nasty when one of my files is an independent module, so that the double-loading creates compilation errors, but Igor hides the offending procedure files.
In fact, that leads me to another suggestion, which is that if there is a compilation error in an independent module when IndependentModuleDev=0, for Igor to automatically offer to set IndependentModuleDev=1 so it will be possible to correct the error.
And if you use the latest version of Igor, when you select Adopt All... from the File menu you get a dialog that has checkboxes to control what gets adopted.
I have adopted all, except for Wavemetrics procedures (just as in the image you attached). However, if I have a procedure I've written that I want to access in all of my experiments, I'll keep an alias of it in Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/, as suggested here: displayhelptopic("igor procedures folder")
This isn't what is referred to as "Wavemetrics procedures", is it? That would be Applications/Igor Pro 6.2 Folder/Wavemetrics Procedures/
If I adopt all (excluding Wavemetrics procedures) and reload the experiment on my own computer, these procedures (with the alias as above) get loaded twice and I have to kill one copy to get the procedures to compile. This is really what I was asking for - a way to exclude these from adopt all (like an "adopt several" dialogue with checkboxes to choose which procedures to adopt), or for Igor to detect whether there are duplicate procedures going to be loaded because the (new) user of the experiment already has them in their Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/ directory as well as adopted in the saved experiment. Most of the files will be procedures I've written, and so the new user probably won't have them in their local directory, but procedures like HDF5 browser they might well have. Some sort of "kill duplicate procedure files" would do the trick.
I can currently save an experiment so it will load fine on someone else's computer without a local copy of all my procedures, but I get duplicates when loading on my computer. I can save without adopting those procedures in Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/, but a different user would have procedures missing. How best I get round this?
Gotcha. That's hard to deal with. Indeed, Igor Procedures is not the same as WaveMetrics Procedures.
The whole point of Adopt All is to make a self-contained experiment file to send to folks. I don't think there is an easy way around this- Igor would have to do a character-by-character comparison to find out if two procedure windows were the same. Since Adopt All severs the connection to the file, Igor can't just check to see if they both point to the same file on your hard drive.
One way around would be to make a single file with #includes for all your procedure files that are presently in Igor Procedures. Put it in User Procedures with a short name. Then you can #include just one file with a short, easy to type name in order to use your own procedures. If you got really ambitious you could make a menu item to load your procedures just like our Packages menus. That involves the use of Execute/P and the INSERT INCLUDE and COMPILE PROCEDURES keywords. To see how we create the Packages menus, look in your Igor Procedures folder at WMMenus.ipf.
March 5, 2012 at 05:40 am - Permalink
John Weeks
WaveMetrics, Inc.
support@wavemetrics.com
March 5, 2012 at 09:44 am - Permalink
I have adopted all, except for Wavemetrics procedures (just as in the image you attached). However, if I have a procedure I've written that I want to access in all of my experiments, I'll keep an alias of it in Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/, as suggested here:
displayhelptopic("igor procedures folder")This isn't what is referred to as "Wavemetrics procedures", is it? That would be Applications/Igor Pro 6.2 Folder/Wavemetrics Procedures/
If I adopt all (excluding Wavemetrics procedures) and reload the experiment on my own computer, these procedures (with the alias as above) get loaded twice and I have to kill one copy to get the procedures to compile. This is really what I was asking for - a way to exclude these from adopt all (like an "adopt several" dialogue with checkboxes to choose which procedures to adopt), or for Igor to detect whether there are duplicate procedures going to be loaded because the (new) user of the experiment already has them in their Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/ directory as well as adopted in the saved experiment. Most of the files will be procedures I've written, and so the new user probably won't have them in their local directory, but procedures like HDF5 browser they might well have. Some sort of "kill duplicate procedure files" would do the trick.
I can currently save an experiment so it will load fine on someone else's computer without a local copy of all my procedures, but I get duplicates when loading on my computer. I can save without adopting those procedures in Documents/Wavemetrics/Igor Pro 6 User Files/Igor Procedures/, but a different user would have procedures missing. How best I get round this?
Thanks
March 6, 2012 at 05:44 am - Permalink
The whole point of Adopt All is to make a self-contained experiment file to send to folks. I don't think there is an easy way around this- Igor would have to do a character-by-character comparison to find out if two procedure windows were the same. Since Adopt All severs the connection to the file, Igor can't just check to see if they both point to the same file on your hard drive.
One way around would be to make a single file with #includes for all your procedure files that are presently in Igor Procedures. Put it in User Procedures with a short name. Then you can #include just one file with a short, easy to type name in order to use your own procedures. If you got really ambitious you could make a menu item to load your procedures just like our Packages menus. That involves the use of Execute/P and the INSERT INCLUDE and COMPILE PROCEDURES keywords. To see how we create the Packages menus, look in your Igor Procedures folder at WMMenus.ipf.
John Weeks
WaveMetrics, Inc.
support@wavemetrics.com
March 6, 2012 at 11:10 am - Permalink
March 7, 2012 at 07:31 am - Permalink