[jawsscripts] Re: how would peoplehandle this
- From: "Sean Randall" <seanr@xxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Mon, 2 Mar 2009 16:17:38 -0000
The reason I suggested focus rather than a specific tab processor was so
that in the event focus was placed onto an undesirable control some other
way (via a mouse, or even a cursor which is sometimes possible) you'd get no
speech if those controls don't talk.
However Dennis' list of drawbacks to focusChange is a good one and the
processing overhead may indeed be too much.
Sean.
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of David Farough
Sent: Monday, March 02, 2009 3:15 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: how would peoplehandle this
This would work ok except that you need to determine in which direction
you are moving. In FocusChangedEvent you are passed the handle of the
current window and the handle of the previously focussed window. So you
would need to determine based on this information which direction you
are moving before setting the focus to the appropriate control.
Another way to handle this would be to create versions of the tabKey
and shiftTabKey functions for your application. This way you do not
need to be concerned about direction. Be sure to invoke the default
versions of these functions when your conditions are not satisfied.
David Farough
__________
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: