Window-Eyes 8.0: New Features Webinar Recording Now Available for Download!Hi
Rick,
I had been all that you have mentioned so far but at first had not
unchecked some of the items. It improved things a little, but no matter what is
done even in Windows 7 the code editor for no reason hangs, sometimes for a
minute until it decides to regain focus.
I don't know why, but that is the issue with the code editor. I still think
something is trying to display, a suggestion or something, what ever it is, it
just hangs the pointer and can not do anything until it comes back...
Thanks for the help, it has made it a little better, but some work to get
focus back immediately would be very helpful.\
Thanks, Bruce
Sent: Tuesday, February 12, 2013 2:53 PM
Subject: Re: Visual Basic 2010 Event List and Window
Hi Rick,
That is what I do to make fast changes in the .vb file before loading the
Designer again. My biggest problem is screen slowness and the cursor not
focusing on the code editor. I get a little upset at that...
Bruce
Sent: Tuesday, February 12, 2013 9:03 AM
Subject: Re: Visual Basic 2010 Event List and Window
Open vb.net ide:
Click New Project under the FileMenu:
I hear Installed Templates Visual Basic and it is selected in the list
(only one in my case) of languages.
I tab and select Windows Forms Application
I tab and enter TestProject for the project name tab and click ok.
I am put into SolutionExplorer and the following structure is listed.
TestProject is the top level folder:
Under that is the My Project folder and the Form1.vb object.
Lets just save our project for another run at making it accessible.
I just hit alt+f4
I am asked if I want to save or discard changes and I cllick save.
The SaveProject Dialog comes up you can tab around to hear the items.
I leave the name as TestProject
I tab and enter c:\ in the location box
I tab and leave the solution name as TestProject
I tab and leave the create directory for project checked (I often uncheck
this but leave it checked for now).
I tab and click the Save button and the project is saved and the IDE closed.
I went under c:\ and found the TestProject folder with the basic modules in
it.
Post me when you get this far.
xpanded 2 items is read and the top level object.
----- Original Message -----
From: BX
To: [email protected]
Sent: Tuesday, February 12, 2013 8:09 AM
Subject: Re: Visual Basic 2010 Event List and Window
Hi Rick,
Last night when I had some errors the cursor and mouse would do
nothing. It sat there for minutes it seemed and just did nothing. So I had to
give up on it. I do not know what is going on for I was just trying to get back
into the code editor for the last run and it would not. The voice at times
seemed to go on like it was on a run-away and once in a while you would get a
chirp or something to indicate the voice is in some kind of infinite loop...
That is the main problem I have with the code editor and Windoweyes.
Bruce
Sent: Tuesday, February 12, 2013 1:02 AM
Subject: Re: Visual Basic 2010 Event List and Window
Hi Bruce: I very, very often use NotePad to create or modify
code if I think I will have allot of changes.
What I do is to copy and paste sample code or other code I have
developed and tested into notepad. Then make the changes and paste them into
the code editor. Then I hit "i" under the View menu and a list of errors will
pop up. I then use the mouse keys to go through them one at a time. I move the
mouse to one of the messages and hit the left mouse click, think twice. That
takes me to the line of code where the error is located inside the code editor.
The messages in the Error list also tell you the class, and method and line
number where the error is located if you want to make a note of it to research
the error later.
I fix that error and then I hit "i" under the view menu to get the
error list again and left click the next error I want to fix. I do this until I
get a clean compile.
Before you start working on a project for the day or for a long
period of time, perhaps a couple of hours, find your project folder then copy
and paste it into the same folder. This will give you a backup copy of the
project in case things go horribly wrong as they have done from time to time.
If you really get stuck in the Forms Designer you can use NVDA in
there and it at least reads much better than WindowEyes.
Some folks said they had no problems with NVDA in the Code Editor but
I couldnt get it to read but again, I have no clue about the hot keys to make
NVDA do anything at all but that is something I was going to look into downline.
The only problem I had running both WindowEyes and NVDA at the same
time was that after using NVDA in the Forms Designer the WindowEyes Mouse keys
seemed to stop working, perhaps I was doing something wrong with NVDA.I
Rebooted or closed vb.net and ReOpened it I dont remember which, to get full
WindowEyes mouse key actions again.
But using the combination of NVDA and WindowEyes showed me things
could be more accessible which is what I was looking at when working on the
vb.net 2010 script.
In any case I can create and deploy vb.net projects using vb.net 2008
so I am guessing 2010 isnt that much different and that is indeed what I have
heard from folks who use it.
If anything is annoying try and let me know and I will see if I can
find a work-around you can live with.
I have done this for so long that I might be taking something for
granted that you might have questions about so dont hesitate to ask if
something doesnt work well enough to get the job done in a timely fashon.
I dont know why the typing would be slow, mine is almost as fast as I
can type. Could be vb.net 2010 or some setting in the options for the code
editor or, if you are unning the new version of WindowEyes some problem with
WindowEyes its hard to tell since there are so many moving parts to the
accessibility puzzle.
Well, keep playing with vb.net and let me know how you are making out.
Also, if you did not change the options for vb.net to reduce some of
the dynamic stuff it may be impacting your use of the code editor. If that is
the case let me know and we can walk through a few of them to see if we can get
that puppy running a little better.
Rick USA
