Then do the same thing in the model widget code.
-Adrian
Bruno Busco wrote:
This would mean to change all the screens! :-(
2009/12/7 Adrian Crum <[email protected]>:
<screen name="MyScreen">
<section>
<actions>
<service service-name="getUserPreferenceGroup">
<field-map field-name="userPrefGroupTypeId"
value="MyScreen"/>
</service>
<set field="screenSettings" from-field="userPrefMap"/>
</actions>
...
</section>
</screen>
Bruno Busco wrote:
Adrian,
sorry for the bad sentence, I couldn't even read myself.
I meant that GLOBAL_PREFERENCES gets already loaded in the
ApplicationDecorator.
So now we have two options to have screenlets with the same id saved
indipendently:
1) Use a screen related userPrefGroupTypeId.
2) Combine the screen name for the preference key
I will work on it...
Thank you,
-Bruno
2009/12/7 Bilgin Ibryam <[email protected]>:
Bruno Busco wrote:
Thank you Adrian,
but then how to the theme loaded easily? The global ones are already
loaded along the selected theme etc.
-Bruno
Or you can combine the screen name and sceenlet id for the preference
key,
instead of (screenlet.id+"_collapsed" )
Bilgin
