As far as I can see, the only restriction introduced by this
solution is that one cannot navigate through the tabEnabled
controls anymore using the arrow keys. But I believe the TAB
/ SHIFT+TAB keys are sufficient for this.
They are. This limitation is expected for component-based
I found a quick (and dirty?) fix to this problem:
In 'onKeyDown' handler method of my custom slidebar I do
Selection.setFocus(this) at the end (surrounded by an if() checking
whether the pressed key was one of UP,DOWN,RIGHT,LEFT). This seems to
override the default focus associated action for
Hi Dan
Thanks for your comments.
The use of arrow keys has been requested by the client. I may have to
try and talk them out of it.
But it makes sense visually - the sliders are arrows pointing left
and right, and it's important that the user can slide them as little
or as much as they
Standard keyboard accessibility states that the tab and
enter key are
the 2 keys that can be used. ie. These map to switch users keys as
standard. So what you can do is tab to the slider and then
on an enter
press the slider can increment an amount and so on, until
the next tab
I think you can use onKillFocus and onSetFocus. When onSetFocus. Your
key listners always update the current focus scrollbar (e.g. set a
reference as currScrollbar) when onSetFocus, currScrollbar=this
On 12/5/06, Dave Wood [EMAIL PROTECTED] wrote:
Hi Dan
Thanks for your comments.
The use of
Hi Andrew
Basically, once the slider gains focus, you then use keys to
control the
slider position. The tab key moves the focus away from the slider.
Here's the shortcuts I'd recommend:
Right arrow and up arrow - increment slider (using right and up allows
the slider to be vertical or
6 matches
Mail list logo
