On 15/06/2009 16:39, Greg Brown wrote:
FWIW, I don't think it makes sense in TextInput - if you find that you
need a read-only TextInput, you should probably be using a Label.
Otherwise, you should probably be disabling your TextInput, so the user
knows that it is actually a text input.
There might be a difference, although it depends on implementation.
I saw some disabled controls that totally forbid user input, which is
annoying: you cannot scroll them, you cannot select text to copy it,
etc. In this case, a read-only mode can make sense.
If your Label supports scrolling and selecting, it might make sense as a
read-only text input. If disabled TextInput supports it, it is indeed
perceived as read-only. Otherwise, the read-only mode can be interesting.
BTW, I wanted to check against your demos, so I went to the Kitchen Sink
one. I had to open it in Safari because for some reason it freezes my
Firefox 3 tonight (it is not the most stable lately).
Anyway, I opened the Text fold, and saw some oddities. Perhaps they have
been fixed already.
The Label doesn't allow selecting, which isn't really surprising, but
the TextArea doesn't allow it either, which is more surprising.
There is another glitch: scroll the demo pane so that the TextArea is
half hidden by the bottom limit of the applet. Scroll the TextArea (with
its scroll bar): the scrolled part goes down to the lower limit of the
applet (including the bottom scroll bar).
Same problem with the Sortable table. But not the Trees.
--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --
