Ticket #683 (closed enhancement: moved)
Opened 2011-07-25T16:07:12-05:00
Last modified 2014-05-01T06:27:29-05:00
Allow parameters to be contextually activated
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | minor | Milestone: | imagej2-unscheduled |
| Component: | Plugin Framework | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1631 |
Description
Some modules may have differing inputs depending on the values of other inputs. For example, a thresholding plugin where you select which thresholding method to use may activate or deactivate certain secondary parameters depending on the method chosen.
We could implement this by adding an "active" boolean state to each input. All inactive inputs are hidden in the UI. Also, all inputs inactive at the time the module is run would not be included when recording a script of that module execution.
Change History
comment:2 Changed 2012-09-06T14:09:33-05:00 by curtis
- Blocking 1357 added; 1052 removed
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5
comment:3 Changed 2013-01-22T16:02:59-06:00 by bdezonia
- Blocking 1631 added; 1357 removed
- Milestone changed from imagej2-b7-ndim-data to imagej2-unscheduled
comment:4 Changed 2014-05-01T06:27:29-05:00 by curtis
- Status changed from new to closed
- Resolution set to moved