Difference: DpHipeTools (38 vs. 39)

Revision 392009-04-30 - JaimeSaiz

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Adding Tools to HIPE

Line: 139 to 139
  Currently the system contains basic implementation for the simple types Integer, Float, Long, Double and few more, so there's still a lot of space for improvements and contribution.
Changed:
<
<
The following behaviours and limitations are present in the provided modifiers:
>
>
Warning, important 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". 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.
Line: 197 to 197
  parameter.setModifier(new MyModifer());
Deleted:
<
<
Warning, important If a modifier is associated to a task parameter in the task constructor, like in the example above, it is instantiated during initialization, when the task is created. This means that the JComponents used for your Modifier may not have the same GUI theme than the application, because the GUI theme is set just after the initialization of the registry. In that case, you may consider to write a custom Signature Component instead, which would be instantiated after the theme is set. Not only the theme is wrong but, as is the case with JComboBoxes (JOptionModifier), the component may not behave properly when actioned.
 

Signature Components

 
This site is powered by the TWiki collaboration platform Powered by Perl