Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Adding Tools to HIPE | ||||||||
Line: 213 to 213 | ||||||||
} | ||||||||
Deleted: | ||||||||
< < | ![]() Using TaskParameter.setModifier() for customizing modifiers is deprecated.This mechanism is unsafe, even dangerous, because it implies executing GUI code at task creation, which is done in a non-GUI thread. In consequence, this method is planned to be removed. | |||||||
Line: 242 to 238 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
and the two implicit contracts inherited by the Extension Registry
| ||||||||
Added: | ||||||||
> > | Conventions for labels for input parameters: to construct the labels of your parameters you can use the static function of class JTaskSignatureComponent public static JLabel getDecoratedLabel(TaskParameter tp, boolean isPrimeInput, String altName)it provides a decorated label (including tooltip) that follows the standard style. For the function to work properly your task parameters should be fully configured (for example, the parameter description will be the tooltip of the label) if present. | |||||||
An easy way of implementing TaskSignatureComponent is by extending ia.task.gui.dialog.JTaskSignatureComponent and providing your own implementation for the makeModifierMap() method.
For example, if you want to use a custom Signature Component that just wants to use ia.gui.apps.modifier.JFilePathModifier for a parameter aimed for a file name, you could do it like this: | ||||||||
Line: 273 to 271 | ||||||||
![]() You no longer need a signature component to choose your own modifiers for your task (and link them with events ...): Task has a new function public Map<String, Modifier> getCustomModifiers()where you can do just that, see above "Register a Modifier". | ||||||||
Deleted: | ||||||||
< < | Conventions for labels for input parameters: (see DM).
The static function public static JLabel getDecoratedLabel(TaskParameter tp, boolean isPrimeInput, String altName)provides a decorated label (including tooltip) that follows the standard style. For the function to work properly your task parameters should be fully configured (for example, the parameter description will be the tooltip of the label) | |||||||
Deleted: | ||||||||
< < | If some other function needs to be made public so that tasks can follow the default style, they will be added above. | |||||||
Register a Task Signature Component | ||||||||
Line: 315 to 309 | ||||||||
| ||||||||
Added: | ||||||||
> > |
public Action getRunAction() { return runbutton.getAction(); } public Action getResetAction() { return resetButton.getAction(); } | |||||||
and the two implicit contracts inherited by the Extension Registry
| ||||||||
Deleted: | ||||||||
< < | ![]() | |||||||
The Rotate Panel example (herschel.ia.task.example.RotatePanel): ![]() | ||||||||
Line: 348 to 350 | ||||||||
Task compliance
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Recommendations for simple tasks and limitations |