> Yeah, it's easy to miss setting the currently selected value > for when DropDownChoice is rendered for the first time. > Hence it's always a good idea to supply it in the > constructor.
I have noticed the problem when I have a propertymodel attached to the dropdown, and I have two chained dropdowns ... I haven't studied it much, could fairly well be a stupid user bug. ** Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
