Re: jaws and VS 2010 revisited
- From: Kerneels Roos <kerneels@xxxxxxxxx>
- To: programmingblind@xxxxxxxxxxxxx
- Date: Thu, 16 Sep 2010 17:21:21 +0200
Hi Varun,
Today I couldn't compile a project because the assembly it links to is from
.Net 4.0 and I understand that the only way for me to link to such
assemblies would be to move up to VS 2010. I presume there should be a way
to compile for .Net 4.0 by only using a command line compiler, but it's just
postponing the inevitable ha ha.
So I'll be joining you there next week! And I'm going to have to see what
NVDA and JAWS 8 is going to do with VS 2010!
My advice is to steer clear of VS by using your own code editor and only
using VS for compiling and debugging.
Has anyone had success with WindowsEyes or any other screen reader when it
comes to VS 2010?
Maybe we should all ditch everything MS and code C++ and C in and for Linux
using speakup in the console!
Or go over to Java in Eclipse, or Python in which ever editor you choose and
feel like.
Keep well
On Thu, Sep 16, 2010 at 8:20 AM, Varun Khosla <varun.lists@xxxxxxxxx> wrote:
> Hi all,
>
> Latest Jaws 11 version seems to be working ok with VS 2010. It's now
> reading code editor properly (although recognizing the collapsed code
> block as space). There's a miner yet most annoying issue I'm facing:
> Jaws for unknown reasons, enters into menu mode (announcing "menu")
> most of the time when I open solution explorer, intellisense and even
> dialog boxes. This strange behavior causes Jaws to read things
> improperly (sort of menu style). Moreover, in case of intellisense,
> when I select an item (say by tabbing), intellisense gets out of the
> way but Jaws doesn't get out of the menu mode and thus unable to read
> the code using arrow keys until I explicitly make it so by pressing
> alt key twice.
> I think the same issue was there with previous versions of Jaws when
> working with earlier VS versions and resolved with some tweaks in the
> 2005 scripts? Does anyone have an idea as to how to fix this?
>
> Finally I've been put into a project being developed on VS 2010 and
> cannot escape. With all of my initial experiences, I advice to try to
> keep yourself away from it as long as you can.
>
> P.S. I earlier put this issue into VS2008 intellisense and jaws thread
> finding it closer to what is being discussed over there, but later I
> felt it would be more appropriate for it to have its own thread.
>
> Thanks,
> Varun
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
--
Kerneels Roos
Cell/SMS: +27 (0)82 309 1998
Skype: cornelis.roos
The early bird may get the worm, but the second mouse gets the cheese!
Other related posts:
