I am fixin' to (southern slang) do another one soon. I've only translated one experiment so far. In the meantime, we are probably meaning the same thing in how best to use AdoptFiles. I had to dig up an older version of the original experiment. I could not recover back to un-adopt the adopted files. My anxiety arose from the case that I forgot to save the working copy before I made the experiment self-contained. I think this covers what I have found to work. Finally, I save the demo experiment.Īt next opening, the demo experiment should be / is self-contained. I then remove the #include directives (comment them out). I then do a call to AdoptFiles *while still in the non working copy*. Once I am happy with the operation, I do a Save As and save the experiment as Demo Experiment - WORKING COPY. At the start, before I adopt the two procedure files, I have to #include them. The demo experiment has a call to each function. They are independent modules (SendtoLayout and SendtoNotebook) with entry point function calls (sendtolayout#layout_frontset() and sendtonotebook#notebook_frontset()). These are general purpose procedure files that I will want to use over and over again. It is self-contained except for two procedure files, Send to Layout.ipf and Send to Notebook.ipf. I suspect that this request may also dovetail with requests for ways to make experiments "stand alone". The tragedy for me is that, every time I develop an experiment that I would like to share with students or colleagues, I have to copy + paste the utility functions into my experiment procedure window. I have utility procedure files that layout graphs + panels, that take snapshots into notebooks, and that scroll through traces. At future compiles, the directive would run the procedure file from the embedded version, ignoring any external file by that name. #bind Īt compile, the directive would load the procedure file (from User's Procedures) and "bind" it into the experiment by storing it within the experiment in some manner. Using the analogy with #pragma directives, I would see this. as a demo package), users do not have to have the corresponding procedure files installed locally. I am wishing for a way to "bind together" procedure files into an experiment file so that, when I distribute the experiment itself (e.g. Wide-Angle Neutron Spin Echo Spectroscopy.
0 kommentar(er)
