Window-Eyes 8.0: New Features Webinar Recording Now Available for Download!Hi: Let me look at them, I know some to shut down and some to leave alone. Also, is vb.net 2010 supported on windows nt? I will post up a little later the next group of tabs to turn off. Keep track of what you turn off so you remember what to turn back on if you decide it doesnt work well with something turned off. Rick USA
----- Original Message ----- From: BX To: [email protected] Sent: Wednesday, February 13, 2013 8:16 AM Subject: Re: Visual Basic 2010 Event List and Window Hi Rick, You are probably right, too many pop-ups that change focus and Windoweyes does not like pop-ups, Avast is one of them, and the cursor never gets back unless you do an alt-a... My system is Windows NT with XP professional and both it and the Windows 7 notebook are 32 bit machines. When going to the Windows 7 the editor worked better but did have it's hang moment, but I think there is one or 2 things I did not disable. I suspect I have to disable anything automatic, with the hope it does... I think there is an error suggestion auto that also can be disabled, I will look at that for I think that one is still active. I did not install SQL, but it did download all the SQL stuff and the Options menu has all the SQL and data base settings there and maybe that is by default. So, will go around and shut everything off! Thanks, I will get the ram size later but do think the XP is only around 250 meg or 300 meg and the notebook is 4 G but not sure. Bruce Sent: Wednesday, February 13, 2013 2:07 AM Subject: Re: Visual Basic 2010 Event List and Window Hi Bruce: The IDE is very dynamic. It opens and closes windows without telling you and moves them and their tags around without telling you. This has a big negative impact on screen readers, at least WindowEyes. The trick is to try and stop all this from happening or to limit it so a screen reader can find things and not worry about overlapping windows at the same time. While in the Code Editor the major problem has been the Error Window or list. This can pop up while you type, try to type, in the Code window and sometimes nothing is read by the screen reader and you only notice some unpredictable behavior like trying to type something and having what you type be entered in the wrong location or not being able to read words or lines using the standard Windows keys and I think even what would appear as slow response. Other windows like the Properties Window and others can overlap or be overlapped while you try and work in them which causes a ping or the inability to be able to work in say a TextBox cleanly without pinging and sometimes not being able to enter or remove data properly. Let me ask you about your machine configuration. What processor are you running ( core-dueo or quad or whatever and what os, think you mentioned Windows 7. Also how much ram and how much available hard disk do you have available? The newer os Windows 7 and Visual Studio, vb.net, are really memory hogs and if you installed sql server express it is a huge memory hog as well. Dont try and uninstall sql server since you can just turn it off and not have any potential problems if your memory is running low. Also, a 32 bit machine requires les memory by half of whatever a 64 bit machine requires. 2 gig is about the absolute minimum to have things run in a decent fashon in a 32 bit environment and I would guess 4 gig for a 64 bit machine. Let me know what your current setup is and I will continue with the simple TestProject so you can determine what is going on. Have you created it, that is a project with a form (note your form needs to be large enough to hold the controls you drop on it and you need to position them so they dont overlap and fit within the boundries of the form as mentioned in my last posting. I use pixels since you know your screen resolution and can ensure everything is fitting on it while analyzing any potential problems with overlaps. If you are this far I will do a little browsing of the options to see what to check out next but first let me know what your computer is, the os, 32 or 64, ram and disk space. Also let me know if you installed sql server express since that could have an impact on performance but is less likely the problem than some dynamic activity within the IDE itself causing the code editor problems. Sorry it takes me so long to figure things out but I am a little slow and methodocal when trying to figure anything out. Rick USA ----- Original Message ----- From: BX To: [email protected] Sent: Tuesday, February 12, 2013 11:56 PM Subject: Re: Visual Basic 2010 Event List and Window 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
