Yeah, I know afinity is not persistent. So, there is that.
But, what I was hoping for is an indication of what the heck is going on,
instead of stoney silence.
But, if interProcess comms don't have a timeout, with sufficient timeout
handling inside jaws, you clearly get hung up via mutual exclusion.
A blocked process doesn't respond to your request, which means you are
blocked too.
Too bad about that. One of the worst aspects to our current screen reader
solutions, is that we are in the mix with everything else going on. Life
without feedback is a common and disconcerting experience.
So it is.
+--------------------------------------------------------------------------+
Listen to The Snowman on MushroomFM.com, Saturday evenings, 8PM Eastern
time.
60's and 70's tunes, and gently conservative talk.
----- Original Message -----
From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Thursday, February 28, 2019 11:50 AM
Subject: [jawsscripts] Re: Jaws speaking information too quick?
I think processor affinity clears each time the process restarts, not just
on every system reboot.
Theoretically, I would not expect a change in processor affinity to effect
how pause or delay work.
As for JAWS freezes caused by other apps:
* You Alt+Tab to an app, or an app freezes while in focus.
* JAWS sends a message to the app, like "Give me your window title" or "Give
me an MSAA object for the focused control."
* The app is too dead to respond at all.
* JAWS hangs waiting for an answer until it gives up and restarts.
That's the most common basic scenario, and it happens to all screen readers
as far as I know. It is not always possible for a screen reader, or a user
for that matter, to tell the difference between an application that needs a
while to finish something, an app that is slow because five other apps are
hogging the CPU to the extreme, and an app that is legitimately locked up
for good.
On Thu, Feb 28, 2019 at 12:42:28PM -0500, James Lockwood 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.
In my experience setting the processor affinity doesn???t maintain its
settings when you restart the computer. That was in Windows 7 however. I
haven???t tried windows 10
On Feb 28, 2019, at 8:51 AM, Doug Lee <doug.lee@xxxxxxxxxxxxxxx> wrote:
If you have time and sufficient curiosity, compare pause() to delay(1, True)
to see if the latter works as pause does. I doubt it does, but that would
complete the test of theory.
On Thu, Feb 28, 2019 at 10:48:40AM -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.
Yes, confusing, but in my scenario pause works, a delay of 1 doesn't, so is
the part that says "
JAWS yields to the time needs of other applications" having the key impact
here? Best steve.
-----Original Message-----
From: Snowman
Sent: Wednesday, February 27, 2019 8:37 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Jaws speaking information too quick?
Right, but that specifically says that pause(), and delay(1) are
equivalent.
I assume that means they are exactly the same.
So, who knows how this really got implemented. I have never seen an app
hold onto the CPU longer than the 100 milliseconds afforded by the pause
statement. but, if you have ever had jaws appear to lockup and stop
spteaking, and who hasn't, you have probably experienced a handoff to
another application, who didn't gracefully give up the cpu, but held it
indefinitely.
I had wondered whether using the windows ability to set processor offinity,
so as to make jaws run in a dedicated processor would obviate situations
like that. But,I have not yet established that as actually working the way
I would expect.
+--------------------------------------------------------------------------+
Listen to The Snowman on MushroomFM.com, Saturday evenings, 8PM Eastern
time.
60's and 70's tunes, and gently conservative talk.
----- Original Message -----
From: "Steve Spamer" <stevespamer68@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Wednesday, February 27, 2019 1:55 PM
Subject: [jawsscripts] Re: Jaws speaking information too quick?
Well Jim, I'm just taking the approach that pause waits until the program is
ready to go again, rather than just delaying for a specified amount of time,
which would wait, but then continue regardless of whether or not the program
is ready. Jaws function description says:
Stops the processing of a script so that other applications can complete
tasks. When a pause function is placed in a script, JAWS yields to the time
needs of other applications. Once other applications have been given the
opportunity to use processing time, then JAWS resumes the script. The pause
function is equivalent to using the Delay function with a value of 1. Do not
place a pause command in a While loop
So, it's like this function interacts with the application somehow.
Best steve.
-----Original Message-----
From: Snowman
Sent: Wednesday, February 27, 2019 6:28 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Jaws speaking information too quick?
I remember this message. But, I glossed over the intriguing possibility of
processing events during the delay. that is a rather remarkable feature.
What I have never been able to determine for sure, is whether pause(), is
equivalent to delay(1). The time interval is the same. But, I'm not sure
about how that affects other threads, or processes.
If Delay is just a big long while loop, then
it would seem to have little benefit since, without yielding the CPU, the
delay won't do anything useful, since the only reason to delay is to give
something else time to do something. And, you have to yield the CPU in
order for anything to happen.
+--------------------------------------------------------------------------+
Listen to The Snowman on MushroomFM.com, Saturday evenings, 8PM Eastern
time.
60's and 70's tunes, and gently conservative talk.
----- Original Message -----
From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Wednesday, February 27, 2019 7:28 AM
Subject: [jawsscripts] Re: Jaws speaking information too quick?
From a message I posted here in December, 2015: