Ticket #2980 (closed: invalid)
Mechanism for specifying "you need to specify one of these X properties" with GUI.
| Reported by: | Janik Zikovsky | Owned by: | Nick Draper |
|---|---|---|---|
| Priority: | major | Milestone: | Release 2.5 |
| Component: | MantidPlot | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: |
Description
In the algorithm you could specify that one of X properties is required (but all are optional).
In the GUI, something would show this (perhaps group them in a box, or use radio buttons and gray out the other options?)
Algorithms such as LoadInstrument, AlignDetectors, SumSpectra and many others have such "pick A or B but not both" options. Making this clearer in the GUI would make it easier on users.
Change History
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:8 Changed 8 years ago by Nick Draper
- Status changed from new to verify
- Resolution set to wontfix
This can be implemented when there is a direct need on a new development
comment:10 Changed 8 years ago by Nick Draper
- Status changed from verify to closed
- Resolution changed from wontfix to invalid
closed
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 3827
"New" tickets moved at the code freeze of iteration 29