Difference: DpHipePreferences (34 vs. 35)

Revision 352014-02-19 - AlvarGarcia

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
Line: 258 to 258
  The framework creates here an empty panel for you, with a message saying that preferences can be found in children categories.
Deleted:
<
<
Note:

Preferences are just released. The still unused fields in the Extension when registering may be used in the future, although for the time being the only foreseen (probable) change is to provide an icon to each category.

 

Read preferences

Line: 340 to 337
 

Listen to changes in preferences

Changed:
<
<
Suppose the user opens an editor component you have developed, then open the preferences dialog, changes some preference related to the presentation of your editor, and press OK.
>
>
Suppose the user opens an editor component you have developed, then opens the preferences dialog, changes some preference related to the presentation of your editor, and presses OK.
  The user would expect that these changes would be applied to the opened editor, not only to editors opened from that moment on.
Line: 362 to 359
 The more common situation may be that you want to migrate some existing property to the new preferences mechanism.

This means that the preference should take the value of the associated property while the user doesn't override it.

Changed:
<
<
After overriden, the saved preference is used and the property is not taken into account.
>
>
After being overridden, the saved preference is used and the property will not be taken into account.
  If this is the case, the only thing you need to do is to add few code when registering the handler of the associated preference. Something like this:
 
This site is powered by the TWiki collaboration platform Powered by Perl