🚀 go-pugleaf

Eric,

stringList is a property in the 'classic' dialog model, not in scriptUI. There's a creation problem with dropdowns in scriptUI in that the property name to use is "items", which throws an error:



l: DropDownList { \ 
items: ['A-Master', 'B-Master'], \ 
preferredSize: [200, 20] }, \



So you'd have to use something like this:



l: DropDownList { \ 
{properties: {items: ['A-Master', 'B-Master']}, \ 
preferredSize: [200, 20] }, \



To show some item after the window has been created, do this:



w = new Window (res); 
w.master.l.selection = 1; 
w.show()



This is one of the reasons why I think that resource strings are a pain. The reason cited most often for using resource strings is that they allow you to separate design features from code. But this separation is also possible without using resoource strings. And ironically, you used code in your res. string. I'd think that the purist would do something like this:



 
... 
... 


l: DropDownList {preferredSize: [200, 20]}, \ 
... 
... 
w = new Window (res); 
w.master.l.add ('item', 'A-Master'); 
w.master.l.add ('item', 'B-Master'); 
w.master.l.selection = 1; 
w.show()



After all, the contents of the array is not part of the design.

Peter