[jawsscripts] Re: Changing and Saving / Restoring Cursors
- From: "Donald Marang" <donald.marang@xxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Thu, 4 Dec 2008 22:55:35 -0500
Thanks everyone for your help. I finally figured out my foolish overlook!
I had not noticed the convenient default script, SayActiveCursor, which says
the active cursor, its position and the restriction (for Invisible and
JAWS). I attached a keystroke to the script and started placing it in
various places throughout my event functions. In less time than it will
take me to type this message, I found the problem. In a short, straight
forward function used to gather info into global variables for the results
dialog, like title and number of pages. I simply forgot the final call to
PCCursor after I did a RestoreCursor. Actually, if this worked properly
like a stack, I don't think a final PCCursor call should be necessary.
This event gets called more frequently than I figured. Previously (last
week), I had called this event from a frame action and had used
ScreenStabilizedEvent to reduce this frequency. Unfortunately, this
function suppressed some valid, fast screen updates, like the search results
matches going from 3 to 0 matches in the address book as you type.
Additionally, I think the flexibility and ease of setting up frames is
powerful, but it seems its dependency on screen resolution is impractical in
many cases.
Don Marang
----- Original Message -----
From: "David Farough" <David.Farough@xxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Thursday, December 04, 2008 12:53 PM
Subject: [jawsscripts] Re: Changing and Saving / Restoring Cursors
> Hi Donald:
>
> What is being said at the end of the ActiveItemChangedEvent is that
> there used to be code here that would perform the processing related to
> these controls. Now this processing is being handled by the
> SayObjectActiveItem internal function.
> Internal means that this functionality is contained within Jfw itself
> and that we do not have the source so we cannot see what is being done
> there.
>
> I suggest, that you put a SayString above the function call to
> SayObjectActiveItem in the default.jss file and then compile it. If you
> hear this string spoken when you press the arrow keys while you are
> focussed in the list view of your application, then you will know that
> the SayObjectActiveItem is the function that you need to modify in your
> application scripts.
>
> If this is the case, then you will need to experiment with some of the
> lv functions to see if any of those functions will yield the results you
> need.
>
> Make sure that you call the SayObjectActiveItem function for controls
> that do not meet conditions in your if statement in this function.
>
> Here is the fsdn entry for SayObjectActiveItem.
>
> Function: SayObjectActiveItem
> Description
> Says the active element in certain controls. For example in a list
> view, it will say the selected item. In a menu, it will say the active
> menu item. In a dialog box, it will say the selected tab.
>
> Returns
> Type: Void
>
>
> Parameters
> Param 1:
> Type: int
> Description: As of JAWS 8.0, TRUE if you wish to have JAWS announce
> positional information such as n of m items, FALSE otherwise.
> Include: Optional
>
>
> Version
> This function is available in the following releases:
>
> JAWS 4.51 and later
> Magic 10.5 and later
>
>
>
>
>
>
> David Farough
> Application Accessibility Coordinator/coordonateur de l'accessibilité
> Information Technology Services Directorate /
> Direction des services d'information technologiques
> Public Service Commission / Commission de la fonction publique
> Email / Courriel: David.Farough@xxxxxxxxxxxxx
> Tel. / Tél: (613) 992-2779
>
>>>> "Donald Marang" <donald.marang@xxxxxxxxx> 10:10 am Thursday,
> December 04, 2008 >>>
> I guess that I should have stated that I have been using JAWS 10 since
> I got
> this urge for this project in October. The FocusChngedEvent was very
> confusing. I didn't take a lot of time deciphering the function, but I
>
> couldn't figured how it called all these events. Perhaps the calls
> that
> start with "Process..." have this effect?
>
> I did notice that at the end of the default ActiveItemChangedEvent had
> the
> following comment:
> "; removed code from this spot for special handling of list view items
> ; in favor of the internal handling using SayObjectActiveItem()"
>
> I don't know what this means and I don't know if this matters?
>
> __________
> 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
>
__________
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: