[jawsscripts] Re: Jaws 10 and message box dialogue

Hi Travis:
I will experiment with that and let you know how it goes.

The thing that puzzles me is that when this dialogue appears, I do not
even hear Jaws speak the Saystrings of "auto" and the Active
configuration.  This makes me wonder if my script is even being used.

this makes me wonder 
Q1 What configuration is being used when Jaws first starts as a service
before I even enter my user id in the login dialogue?
q2  At what point in the login does Jaws actually begin to use the
configuration settings in my user folder?

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 

>>> "Travis Roth" <travis@xxxxxxxxxxxxxx> 07:33 pm Tuesday, September
23, 2008 >>>
Hi,

My thought is that there is a possibility the JAWS AutoStartEvent() is
being
triggered before the dialog appears, thus when the code runs it is
finding
nothing to say.

If this is the case I'd suggest putting a check in the AutoStartEvent()
to
check if the dialog is displayed yet, and if not, loop or otherwise
schedule
the dialog reading function to try again in a moment or two.
An if ... pause() may work although this could bog down JAWS and the
program, so using ScheduleFunction() may be a better solution.


-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx 
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of David Farough
Sent: Tuesday, September 23, 2008 3:12 PM
To: jawsscripts@xxxxxxxxxxxxx 
Subject: [jawsscripts] Jaws 10 and message box dialogue

First of all I have sent this to the Jaws beta team but am not sure
whether it will be addressed or not given that this is an in house
application.  This may take a while to describe so I hope that those
who
are interested will bare with me.

Due to security requirements where I work, it has been decided that
early in the login process all users will be presented with a dialogue
which contains the time and date that they last logged in to the
network.  It is up to the individual to contact our I T help desk if
this information is not the time you last logged in.  The application
which does this is written in dot net.  Originally this dialogue was
not
being read by Jaws, so the developer set it up to look for a key in
the
registry that indicates a Jaws user.  If the key is found, the
application displays this message using a standard message box.

This process worked fine until the release of the Jaws 10 beta.  Now
the dialogue is silent.  If I go into home row mode, the class of the
window returned is: 
WindowsForms10.Window.8.app.0.378734a
If I move one window back in the Hierarchy, I get the class #32770
which is what Jaws expects to see as a dialogue.  The
SayWindowTypeAndText will then read the dialogue correctly.

Now I need to get Jaws to do this automatically when the dialogue
appears.  This should be easy, but I can't get it to work.  I think
that
it is because this is happening so early in the login process that
Jaws
is not using the right configuration.

I put the following script in the pwdNotifier.JSS and compiled it.


Void Function AutoStartEvent ()
saystring (GetActiveConfiguration ())
saystring ("auto")
SayWindowTypeAndText (GetPriorWindow (GetFocus ()))

EndFunction


I compiled this and then put the .jsb file in the shared user settings
as well as my user settings folder.

When this dialogue comes up in my login process Jaws does not speak
any
of the saystrings in the autostart event and it does not speak the
dialogue either.

I should also point out, that if I run this program once my login has
completed, that the script works properly and the SayStrings are
spoken
and the dialogue is spoken properly.


To give you an idea, how early in the login this dialogue appears, it
happens immediately following the windows startup sound.  the network
mappings are being established and nothing else will happen in your
login sequence until you hit enter on the ok button.

Can anyone suggest what I can do to resolve this?

I am thinking of asking the developer of this program to unload the
.net window to see if that will resolve the focus issue.

One other thing.  When the dialogue is displayed, the dialogue does
actually have focus (the title bar is highlighted).  when I run this
normally from windows, the ok button has focus.




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 

100 Years Merits a Celebration!  
http://www.psc-cfp.gc.ca/100/index-eng.htm 
100 ans, ça mérite une célébration!    
http://www.psc-cfp.gc.ca/100/index-fra.htm 

__________ 
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 


100 Years Merits a Celebration!  
http://www.psc-cfp.gc.ca/100/index-eng.htm 
100 ans, ça mérite une célébration!    
http://www.psc-cfp.gc.ca/100/index-fra.htm 

__________ 
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: