I don't think Audacity would change the resolution. I hope not!
Glad you got it working. I don't understand why that would affect
anything. I haven't activated the combined meter toolbar. I just did.
It didn't cause that, but something else happened I have seen before
that I don't have the faintest why is happening. The text JAWS gets
from the position controls loses the letters and punctuation, so you
just hear a bunch of digits (because the formatting code in
GetPositionField stops working because it doesn't have the letters and
punctuation). When you look with the JAWS cursor at the selection bar
it sees the same (just numbers, no dots or letters). (They do appear on
the screen visually.) When you move focus to it it reads the letters
and punctuation, but when you do SayLine it sees only the numbers. I
think I may have seen it resolve on its own, but most of the time I have
to shut down and restart Audacity. I don't know any way to cause it to
happen, which is partly why I am documenting it here since it just
happened. I think I have some notes on it somewhere. GetPositionField
gets the text with GetWindowText(hWnd, 0). I think I found some way to
get the string correctly with something in MSAA, and I hope I wrote it
down.
Gary
On 9/6/2015 5:48 PM, David Engebretson Jr. wrote:
I changed my resolution back to a lower setting and it worked. I think someone might have changed the resolution without me knowing. They probably didn't know it would affect JAWS. It's interesting, though, because it seemed like the issue started happening after I enabled the new combined meter under view-> toolbars. Audacity wouldn't change the resolution on its own would it?
Your description of the algorithm is quite helpful. Maybe I'll try and use your routine to find the track panel after saving a project. JAWS totally loses focus. The best I can do is go to the desktop and restart Audacity. Then the track panel comes back into focus. It's interesting, though, that not everyone is complaining about this issue. It makes me think I'm either running a crazy video card or there are gremlins in my puter.
Regarding skype - that would be great. Haven't talked to you in a few years it seems. Sunday the 13th we, at the Washington Council of the Blind, are having a parenting conference call. It's for blind parents. You interested in joining us?
Peace,
d
*From:* Gary Campbell <mailto:campg2003@xxxxxxxxx>
*Sent:* Sunday, September 06, 2015 4:21 PM
*To:* audacity4blind@xxxxxxxxxxxxx <mailto:audacity4blind@xxxxxxxxxxxxx>
*Subject:* [audacity4blind] Re: warnings
Hi David,
I don't know what's going on yet, but the last time I ran Audacity I didn't have the problem with JAWS 16.0.4350 on Win8.1 64-bit laptop, but here's what causes that message, at least for the SayActiveCursor script. JAWS finds the real window of the focused window (the track panel). It then searches for the control ID of the selection control (ID_SELECTION_END) and goes forward 2 controls. It doesn't check any of these. It then calls GetPositionField on this control, which returns the value to speak as a string. GetPositionField processes the value of the control to make it sound nicer. So there's several things that could happen that would cause this message. If it didn't find a real window, or didn't find the selection end control, or didn't get a control when it skipped the two controls, or if somehow the algorithm that processes the string came up with an empty string, the message would occur. The idea behind the message is that if the toolbar isn't selected it won't find the selection end control. Throwing in the processing of the value was, I think, just something easy to catch that error. After all, they always told me I wasted too much time testing for things that wouldn't happen! :-). I just tried it and it works for me. I actually had work last week, and I think I'll have one more day Tuesday. We could try using Skype and Tandem tomorrow or after Tuesday if you want. (I've never done that, but the docs sound like it should work.) Or try getting your feet wet by taking a stab at finding it. I think I'd start by sticking SayInteger() calls to make sure you're going down the path to find the control. Then a SayString to see what the actual control value is. If there is one, then follow through the nightmare in GetPositionField. Get hold of me off list and let me know what you want to do.
Gary
On 8/26/2015 3:34 AM, David Engebretson Jr. wrote:
I've been using the latest Audacity with JAWS scripts. If I press alt+del to here the current time/position, I get a warning saying "to use this feature you must enable the selection toolbar".
I have the selection bar enabled under the View->Toolbars menu...
Another symptom is that, when I use the arrow keys to navigate through a track/project, the time is not announced.
Any idears why this might be happening?
Best,
David