| Behaviour of disabled form fields [message #579590] |
Mon, 29 March 2010 21:03  |
Eclipse User |
|
|
|
Disabled fields on forms never get the focus using the keyboard (only clicking into such a field assigns the focus to it). It would be nice to be able to use the tab key to also cycle through disabled form fields.
Generalized questions:
What behaviour should be supported for disabled form fields? What is the best default behaviour? How to integrate support for this in Scout SDK?
|
|
|
| Re: Behaviour of disabled form fields [message #579633 is a reply to message #579590] |
Tue, 30 March 2010 04:44  |
| Eclipse User |
|
|
|
In ui's this is (normally) done using the properties
enabled
editable
focusable
setting these properties for every field is annoying and of little sense. Therefore eclipse scout generalizes these behaviours to the following two default cases:
1) scout field with enabled=true, attached gui (should) behave as follows:
field can be focus-traversed (with TAB key), focus can be set by mouse click, field content can be copy/pasted. Field content can be edited. Field appears as ready for input .
2) scout field with enabled=false, attached gui (should) behave as follows:
field can not be focus-traversed (with TAB key), focus can be set by mouse click, field content can be copy/pasted.
Field content cannot be edited. Field appears gray, resp. not ready for input.
Please note that this means for swing and swt implementations, that on JComponent / Widget level the setEnabled(false) is normally not used as it disables on-mouse-click focus as well as copy/paste of content on disabled fields.
|
|
|
Powered by
FUDForum. Page generated in 0.03710 seconds
Home