Juan,
You can't block all MSAA events in one swoop, but you can use
ConnectObject for quicker access. For example, instead of doing:
ConnectEvent MSAAEventSource, "Event1", "Function1"
ConnectEvent MSAAEventSource, "Event2", "Function2"
ConnectEvent MSAAEventSource, "Event3", "Function3"
And so on, you could just do:
ConnectObject MSAAEventSource, "MSAA_"
Then, access all the MSAA Events with function names like:
Function MSAA_OnObjectFocus
Function MSAA_OnObjectStateChange
Function MSAA_OnObjectSelection
And so on. That makes things a little cleaner if you're handling a lot
of MSAA events. Alternatively, since all MSAA events pass only one
parameter, you could use multiple ConnectEvent calls for each MSAA event
you're interested in using the same function, like:
ConnectEvent MSAAEventSource, "Event1", "Function1"
ConnectEvent MSAAEventSource, "Event2", "Function1"
ConnectEvent MSAAEventSource, "Event3", "Function1"
Then, in Function1, you would need to note which event is happening, and
handle it accordingly.
If you're looking to block an MSAA event from Window-Eyes, so that you
can handle it completely (rather than just re-acting when an event
happens), read through the MSAAEventSource.BlockEvent method. I believe
there's an example that demonstrates how to block an event from
Window-Eyes, handle it yourself for a specific instance, and pass
everything else on to Window-Eyes.
Aaron
Juan Hernandez wrote:
Thanks Aaron,
I'm starting to get an idea of what I am going to do. One question, can I
block all MSAA events in the app?i I see I can block 1 at a time.
Because I'm having issue figuring out what event is causing my head aches.
Or do I just block individually each msaa event?
-----Original Message-----
From: Aaron Smith [mailto:[email protected]]
Sent: Tuesday, December 16, 2008 05:48 AM
To: [email protected]
Subject: Re: msaa event source
Juan,
You'll have to handle all the focus events yourself, and then decide which
ones you want to speak, and which ones you want to throw away.
Aaron
Juan Hernandez wrote:
Hi Aaron,
So I loaded up the We Event script, and noticed, that on each
OnObjectFocus msaaeventsource event fire, I get anywhere from 2-3
onspeah events firing, I'll get the speak event firing from with in my
onobjectfocus event, and 1-2 times out-side of this event a onspeak
event firing speaking just saying the focused item name... How can I
prevent these other firings?
Thanks, and I hope this makes sence.
Juan
-----Original Message-----
From: Aaron Smith [mailto:[email protected]]
Sent: Wednesday, December 10, 2008 07:44 AM
To: [email protected]
Subject: Re: msaa event source
Juan,
How you debug is up to you. You can use the OutputDebugString and
output to a debugger (like DbgView), or you can use the Speak method
to speak a string when you need to know what's going on. You could
also use the Scripting.FileSystemObject object to write to a file (or
the OutputDebugFile in the toolkit). There are lots of ways to debug.
You might take a look at the Script Errors and Debugging section of
the Window-Eyes Scripting manual for additional information on the
basics of debugging.
Aaron
On 12/10/2008 10:36 AM, Juan Hernandez wrote:
Hi Aaron,
So what do you mean by put in some debug? Does window-eyes have
monitor methods for checcking event information? Sorry about the
stupid
questions.
-----Original Message-----
From: Aaron Smith [mailto:[email protected]]
Sent: Wednesday, December 10, 2008 05:34 AM
To: [email protected]
Subject: Re: msaa event source
Juan,
That's probably overkill. I would put in some debug to see exactly
why you're getting double speech. Are you getting multiple events
causing you to speak twice, or are you speaking during different events,
or what?
Aaron
Juan Hernandez wrote:
Hi all,
I'm trying to build some functionality into itunes via wineyes
scripts, I'm having an issue when I connect the msaaevent, things
double read, like the item list view, it'll say the item like name
song
name song...
So what I'm thinking is to resolve this, and let me know if it is
too crazy, via onspeech event, handle the speech before it is
spoken. is this a good plan if window-eyes is not speaking things
how I'd like them to be spoken?
Thanks.
Juan Hernandez
[email protected]<mailto:[email protected]>
858-699-2105
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the
GW Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support& Web Development
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information pertinent to
your situation when submitting a problem report to the GW Micro Technical
Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
