Re: accessibility issues
- From: "Tyler Littlefield" <tyler@xxxxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 11 Jan 2009 20:07:21 -0700
I finally figured it out, after tweaking the jaws scripts some.
I didn't set it up in the jaws scripts cause I wasn't sure how, but for anyone
interested and having the same issue go to view, then full screen.
Jaws reads call stack great after that.
Gdb is an idea though, I'll have to try that. Maybe I can make vs run a program
to make the binary and store it in a separate directory or something... would
be worth looking in to.
Thanks,
Tyler Littlefield
http://tysdomain.com
----- Original Message -----
From: Ken Perry
To: programmingblind@xxxxxxxxxxxxx
Sent: Sunday, January 11, 2009 7:53 PM
Subject: RE: accessibility issues
When I run into stuff like this with VS I end up just putting up a message
box or printing to a log . So in this case you can just stick a print or a log
any where you think the function is getting called and print out whatever you
like. This will get around any debugger issues. Other than that you could
compile with mingw and use gdb to debug which prints out a nice call stack no
accessibility issues.
Ken
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Tyler Littlefield
Sent: Sunday, January 11, 2009 9:03 PM
To: BlindGeeks@xxxxxxxxxxxxxxx
Subject: vs:accessibility issues
Hello list,
I've got a quick question.
I'm getting an access writing violation in a c++ app I'm working on.
It shows which line triggered the error, but what I'm trying to do is look at
the call stack to see which function called the function where there is an
error.
When I go to debug->windows->call stack, jaws doesn't read a thing, and
virtualizing the window doesn't help because it shows half code half everything
else.
Your help here would be really appriciated, I was on a roll until this popped
up.
Thanks,
Tyler Littlefield
http://tysdomain.com
__________ NOD32 3757 (20090111) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
Other related posts:
