Skip to content
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

Add version of the RawInputDialog which allows saving of settings under a set name #443

Open
4 tasks
lauramurgatroyd opened this issue Dec 10, 2024 · 1 comment · May be fixed by #444
Open
4 tasks

Add version of the RawInputDialog which allows saving of settings under a set name #443

lauramurgatroyd opened this issue Dec 10, 2024 · 1 comment · May be fixed by #444
Assignees

Comments

@lauramurgatroyd
Copy link
Member

  • Make a child of

class RawInputDialog(FormDialog):

and give it a good name!

  • Add an entry widget to allow user to optionally name their current settings
  • Add a dropdown to allow user to select previously named setting
  • Add a button to allow loading of previously named setting

In the backend QSettings will be used to save the dialog settings under a name chosen by the user and allow them to reload them.

Motivation
Specifically motivated by a specific user data project:
Say I had some datasets A, B and C and for each of these I made 3 reconstructions: A1, A2, A3, B1, B2, B3 etc.

Datasets A, B and C are different sizes so have different settings for the raw dialog.
A1, A2, A3 are the same size but are different files, so they have the same settings for the raw dialog but have different filenames. When I load each of A1, A2, A3 I need to use the same settings but select a different file location. Therefore I want to be able to reload past settigns easily, but not have them tied to a filename. Therefore I want to be able to name the setting myself so I can retrieve it.

@lauramurgatroyd lauramurgatroyd self-assigned this Dec 10, 2024
@lauramurgatroyd
Copy link
Member Author

Image

@lauramurgatroyd lauramurgatroyd linked a pull request Dec 10, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant