| |
| META TOPICPARENT |
name="DpHipe" |
Adding Tools to HIPE |
| |
The following behaviours and limitations are present in the provided modifiers:
- If the value is unfilled or invalid (red) the parameter will not used (but see D'n'D). This has been retrofitted in a consistent manner after 1.0
|
|
<
< |
- While you can always in Console write "SomeTask(param = null)", with a Panel you will get "Task()": for GUIs "null is not allowed"
- Modifiers have no notion of the optionality of parameters: if they have a valid value they will return it. So parameters with valid default values will be committed even if optional(if not modified/invalidated)
- All Modifiers accept D'n'D of variables and if a variable is D'n'Ded and stored it takes precedence over the filled value: currently only the default modifier has visual feedback about it's D'n'D state.
|
>
> |
- While you can always in Console write "SomeTask(param = null)", with a Panel you will get "Task()": for GUIs "null is not allowed". The task machinery will take nulls as if the parameter has been ignored by the user.
- Modifiers have no notion of the optionality of parameters: if they have a valid value they will return it. The task machinery will not generate a parameter assignment if the value equals the default.
- All Modifiers accept D'n'D of variables and if a variable is D'n'Ded and stored it takes precedence over the filled value: currently only the default modifier has visual feedback about it's D'n'D state.
|
| |
- Speciallized modifiers:
- Will only store variables compatible with the type.
|
|
<
< |
-
- They do not seem to accept null (to check)
|
>
> |
-
- They do not seem to accept variables set to None (to check)
|
| |
-
- Once a variable has been accepted the value the user edits will forever be ignored
- Cannot forget the variable (default can't either but has no editor).
- JDefaultModifier: (D'n'D can block some Drops, but basically accepts any type)
- Initially they have no type
- They accept the type of the first variable D'n'Ded and remember it (of any type!)
- Now they only accept variables of the same type (or compatible)
|
|
<
< |
-
- You can erase the type D'n'Ding a null (None)
|
>
> |
-
- You can erase the type D'n'Ding a None
|
| |
- Current floating point modifiers are incapable of parsing some special values like NaN, +-Infinite and -0, as parsing/checking is done via pure numeric patterns.
If your Task Parameter isn't one of the mentioned types, you could: |
