You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a mechanism where one could launch a GSASIIscriptable script from the GUI. This would allow users to create their own extended functionality and integrate that into GSAS-II operation.
I am imagining that one could pass in a .gpx file either as a command-line argument or via an environment variable. The file would need to be saved before calling the script and reloaded afterwards.
The other thing that I am not sure how to handle is making sure the usual import statements would still work so that the script can be launched either directly from Python or from inside GSAS-II.
Another thought here is that one could have a mechanism to detect such scripts and then place commands into a the menu as a way to customize GSAS-II with external scripts.
It would be nice to have a mechanism where one could launch a GSASIIscriptable script from the GUI. This would allow users to create their own extended functionality and integrate that into GSAS-II operation.
I am imagining that one could pass in a .gpx file either as a command-line argument or via an environment variable. The file would need to be saved before calling the script and reloaded afterwards.
The other thing that I am not sure how to handle is making sure the usual import statements would still work so that the script can be launched either directly from Python or from inside GSAS-II.
Another thought here is that one could have a mechanism to detect such scripts and then place commands into a the menu as a way to customize GSAS-II with external scripts.