The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.

From:

 Tom Kingston <tom.kingston@charter.net>

Subject:

 Re: Tracing in Visual Studio 2010 Pro

Date:

 Wed, May 23, 2012 7:12:27 pm
Well, this sounds like a big brother bug to me. I don't use Visual
Studio so I can't check it out. But just for the heck of it, I'd try
turning off apps and see if you still have the same problem. Then I'd
take Window-Eyes out of the SysTray so you'd have it in the Alt-Tab
order and see if you can get at it that way. Otherwise I haven't a clue
as to what would be blocking access to it and locking things up.

Hth,
Tom


On 5/23/2012 5:56 PM, Tim Burgess wrote:
> Hi Tom,
>
> Well, it would seem I've stumbled across a larger problem. This is what I
> tried:
>
> 1 - Loaded up W-E 7.5.4;
>
> 2 - Loaded VS2010 Professional;
>
> 3 - Loaded my c++ project;
>
> 4 - Set a break point in a code module;
>
> 5 - Pressed F5 to build and run the project in debug mode;
>
> 6 - Once the target application had successfully built and appeared in the
> foreground, I selected options within it that would force the code to
> encounter the break point. Execution passed back to VS2010 with the focus
> set on the line of code at the break point;
>
> 7 - Pressed Ctrl+Backslash to bring up the W-E Control Panel prior to trying
> your custom highlight definition steps. Unfortunately, the Control Panel
> didn't appear and everything froze. I loaded another product and found that
> I could shut down debug mode then W-E came back to life.
>
>
> Thought I'd better report this experience. O/S is Windows 7/32.
>
> Best wishes.
>
> Tim Burgess
> Raised Bar Ltd
> Phone: +44 (0)1827 719822
>
> Don't forget to vote for improved access to music and music technology at
>
> http://www.raisedbar.net/petition.htm
>
>
>
> -----Original Message-----
> From: Tom Kingston [mailto:tom.kingston@charter.net]
> Sent: 19 May 2012 09:38
> To: gw-scripting@gwmicro.com
> Subject: Re: Tracing in Visual Studio 2010 Pro
>
> No problem. I hope it's helpful. I've tried to ward off the a script is the
> answer to everything outlook. So I look to set files first. And they're
> often much quicker, easier, and more dependable.
>
> Regards,
> Tom
>
>
> On 5/19/2012 4:31 AM, Tim Burgess wrote:
>> That's very helpful - thanks Tom. I've pretty much forgotten
>> everything I knew about Window-Eyes, so I've got to get back up to speed
> fast.
>>
>> Best wishes.
>>
>> Tim Burgess
>> Raised Bar Ltd
>> Phone: +44 (0)1827 719822
>>
>> Don't forget to vote for improved access to music and music technology
>> at
>>
>> http://www.raisedbar.net/petition.htm
>>
>>
>>
>> -----Original Message-----
>> From: Tom Kingston [mailto:tom.kingston@charter.net]
>> Sent: 19 May 2012 09:23
>> To: gw-scripting@gwmicro.com
>> Subject: Re: Tracing in Visual Studio 2010 Pro
>>
>> I haven't done this for years, but if the cursor is replaced by a
>> highlight you can set highlight to on under General, Highlight. This
>> tells Window-Eyes to look for a highlight with the arrows, tab, and
>> control-tab keys. You may also have to manually set the highlight
>> color for the window. Or, not knowing anything about exactly what
>> you're dealing with, if each line is highlighted you could set the
>> cursor keys to read highlight or define a speak window with its attributes
> set to the highlight colors.
>>
>> Hth,
>> Tom
>>
>>
>> On 5/19/2012 1:18 AM, Tim Burgess wrote:
>>> OK,
>>>
>>> It's been a couple of years since I last wrote any Window-Eyes script
>>> code, so I guess I now have the excuse to spend the time to listen to
>>> Chip's tutorials. I'm under time pressure for this c++ project, but I
>>> guess there's no known quick fix.
>>>
>>> Best wishes.
>>>
>>> Tim Burgess
>>>
>>> Raised Bar Ltd
>>>
>>> Phone: +44 (0)1827 719822
>>>
>>> Don't forget to vote for improved access to music and music
>>> technology at
>>>
>>> http://www.raisedbar.net/petition.htm
>>>
>>> *From:*RicksPlace [mailto:ofbgmail@mi.rr.com]
>>> *Sent:* 18 May 2012 09:11
>>> *To:* gw-scripting@gwmicro.com
>>> *Subject:* Re: Tracing in Visual Studio 2010 Pro
>>>
>>> Perhaps a script would work.
>>>
>>> It is likely either a graphic or color indicates the point of
>>> interest in the code base and should be able to be found so long as
>>> it is
>> consistent.
>>>
>>> Let me know how it works when you get there since I will be working
>>> with the debugger some day and will need to create some script code
>>> to avoid accessibility issues with that real-time feature myself.
>>>
>>> Rick USA
>>>
>>
>>
>>
>
>
>