I have not performed the originally recommended test from this thread, but my
experience tells me:
* WindowCreatedEvent is only called when a window is actually created, and
WindowDestroyedEvent when one, or a tree of them, is destroyed.
* Windows can be created and destroyed very often, and at times one might not
expect. It is therefore important to minimize code in these events.
* You can check the window class in WindowCreatedEvent to find out if the
window is yours. Other properties may and may not work immediately or reliably.
On Thu, Mar 21, 2019 at 11:02:54AM -0000, Steve Spamer wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Jim. Not the same scenario, but I have previously put some test lines in
windows created event to see if it could be used to indicate specific things
to me in the past. This is in Samplitude and I do remember that even if the
Pc was idol for a few seconds/minutes, this event was being executed
randomly in the program. Whether or not it was picking up external changes
outside of Samplitude, or whether Samplitude was doing something I didn't
know about, but I remember thinking this shouldn't be executing, as no
windows are being created. I have also had this with windows destroyed
event as well. The test lines would speak, even though I wasn't doing
anything. Maybe not the same, but thought I'd mention it. Best Steve.
-----Original Message-----
From: Snowman
Sent: Wednesday, March 20, 2019 10:42 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] WindowCreatedEvent
Have you guys ever seen this?
I think windowCreatedEvent is being called repeatedly under some
circumstances.
It should only be called once, when a new window is created.
Edit notepad scripts, and add a WindowCreatedEvent, with the same parameter
list as the version in default.jss
And, be a nice guy, and call that default version from your custom version.
But, also, put your favorite beep routine in there so you will get an
audible indication when the event runs.
Back in notepad, as you edit the text, all is well. But, activate the
menu, and down arrow into the file menu.
Now, jaws 2019 starts calling WindowCreatedEvent repeatedly, something like
30 or 40 times per second, whenever jaws is speaking. You can even exit the
menu, and go back to your document. The event is silent until you cause
speech. Even just activating jaws or pc cursor will do it. Once you do
that, the event starts triggering, and keeps doing it until speech stops.
This is way out weird, and I wonder if you guys see this.
This is jaws 2019 on windows 7 64-bit.
__________???
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________???
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
--
Doug Lee, Lead Accessibility Architect
Level Access - over 1,000 organizations trust us to help them achieve and
maintain digital accessibility compliance!
mailto:Doug.Lee@xxxxxxxxxxxxxxx http://www.LevelAccess.com
"While they were saying among themselves it cannot be done, it was done."
--Helen Keller
The State of Digital Accessibility 2019 report is here! Download the report
today to read the findings.
https://levelaccess.com/state-of-digital-accessibility-2019
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts