New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SANS: Save the content of the UI to a user file #3058
Comments
@NickDraper (2011-04-27T07:35:42): @NickDraper (2011-06-27T08:20:15): @NickDraper (2011-09-19T09:30:19): @Anders-Markvardsen (2011-11-02T15:06:06): @NickDraper (2012-01-09T09:45:07): @NickDraper (2012-04-30T14:16:01): @NickDraper (2012-08-10T12:45:19): @NickDraper (2012-10-28T11:42:49): @NickDraper (2013-01-28T09:25:16): @NickDraper (2013-04-29T09:50:12): @NickDraper (2013-07-26T13:59:12): @NickDraper (2014-02-14T11:07:59): @NickDraper (2014-03-07T16:20:31): |
Alternatively we could save the states in a file (which we currently do in the Writing the settings into a user file seems more involved. If this is the way the users want to go ahead however, then we should not start work on this before we have designed and implemented the new user file format |
This is highly likely to be implemented during the joint reflectometry/SANS user file update detailed here #18826 |
Replaced by #18826 |
Alphabetised test file names and merged workspacenaming test files into one
Added unit tests for group pair context
Added unit tests for group pair context
Added muon difference and muon base test files. Removed unnecessary tests
Added muon difference and muon base test files. Removed unnecessary tests
Added muon difference and muon base test files. Removed unnecessary tests
sans_feature
This issue was originally TRAC 2211
Allow users to save the content of the UI to a new user file.
We would have to think about how we keep the original notes & comments in the file. Perhaps the whole previous files at the end, all commented out? Or can you be more clever?
Possibly taking the original file as a base and editing the values in place (may be harder for mask lines).
The text was updated successfully, but these errors were encountered: