Le 25/03/2015 15:04, Hilaire a écrit :
Le 25/03/2015 12:39, Alain Plantec via Pharo-users a écrit :
settingInputWidgetForNode: aSettingDeclaration ^ (aSettingDeclaration name, 'Widget') asSymbol value: self.
strange that you send the #value: message to a Symbol here. Alain It is tricky indeed, but it is the only way I found to by-pass the limitation for customized widget: as I understood it, settings browser expects one class (a type) per dedicated widget. I can latter create a dedicated class for each drop list morph I need in the settings browser, then remove this strange by-pass, I am still exploring. Nevertheless, it does not seem related to the model problem I exposed previously.
Thanks
Hilaire
As I wrote previously, the Settings browser let me complete almost successfully what I need. See attached screenshot. I am only stuck with widget model explicitly set to the SettingDeclaration. Thanks -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
