Hi Greg, thanks for the help ... but with your answers i guess there isn't the concept of a read-only mode for elements (look at normal objects, not disabled, but with selection not changeable by the user) ... is this wanted or is a missing feature ? For example could i implement this as a simple listener that always return without changing the element selection (and maybe in a general way, so we can reuse it), without changing components API ?
For this I'm also looking at the read only property of (some) HTML Form elements ... and at least for some basic elements could be useful, like Text Inputs, etc ... For a user point of view, disabled means "Not available" , "Not applicable", etc, while read-only it's another thing ... and in this case for example Substance has optional markers to decorate the related fields, making more evident to the user that he/she can't modify the value, but can use it like expand it (think at a Combo box) etc, while maybe some background logic in the application could update its values. What do you (and others) say ? > Selected state and checked state are maintained independently. It is possible > for an item > to be checked and not selected, and vice versa. Ok, no problem ... i think this could be a little confusing, but for me is Ok. >> - in TextInputValidatorTest, in the textinputFloatRange I've seen that >> giving inputs in the current Locale all works good, but I haven't find >> a way to change the Locale, or to set a different format to validators >> ... how can i do this ? > > Noel may be able to comment on this one. Ok, I'll wait his feedback ... Bye, Sandro
