Oh I doubt you forgot anything. I am something of a amateur programmer is all, the sort who writes small solutions for computing problems I encounter in my real life. Back in the days of DOS and CP/M all I had to learn was how to address the screen and the language syntax and programming concepts. That is the easy stuff these days of the IDE. I am sure it is easier for sighted people to point and click and drag a control here and click there to adjust the properties there but I am afraid I get lost in the interface long before I get any decent running code. Dale Leavens, Cochrane Ontario Canada DLeavens@xxxxxxx Skype DaleLeavens Come and meet Aurora, Nakita and Nanook at our polar bear habitat. ----- Original Message ----- From: "Andy B" <a_borka@xxxxxxxxxxxxx> To: <programmingblind@xxxxxxxxxxxxx> Sent: Saturday, October 13, 2007 4:31 PM Subject: RE: The top three big problems Good memory I guess... I am in VS2005 almost 50% of the day so have some experience with it. Did I remember something wrong? -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Dale Leavens Sent: Saturday, October 13, 2007 4:27 PM To: programmingblind@xxxxxxxxxxxxx Subject: Re: The top three big problems I want to know how you can possibly remember all those key strokes and the sequence. Dale Leavens, Cochrane Ontario Canada DLeavens@xxxxxxx Skype DaleLeavens Come and meet Aurora, Nakita and Nanook at our polar bear habitat. ----- Original Message ----- From: "Andy B" <a_borka@xxxxxxxxxxxxx> To: <programmingblind@xxxxxxxxxxxxx> Sent: Saturday, October 13, 2007 2:04 PM Subject: RE: The top three big problems The below is easily possible in vs2005 at least. If you go into the settings, under bu8ild options somewhere (I forgot exactly since I haven't been there in a long time), there is a choice to allow the compiler to show the error list/window upon build/compile failure. When you are in this list, hitting enter on a error message actually instantly jumps you to the code line where the error is and highlights it in a certain color. I know the color doesn't help a total blind person, but at least jaws jumps to the exact line being complained about. All you have to do now is hide the error window (alt shift h), fix the line of code and then press f5/control f5/f6 to rebuild again... 2. The usability. A programming environment should be made thinking to the blind programmers needs also, and a blind programmer should be able to configure the environment as he wants. For example, what does a sighted programmer after he runs a program in Eclipse or VS.net and it gives an error? I think that he looks too se what was the error. So, for the sighted programmer is easy to take a look in the wanted pane, but a blind programmer should be able to configure the application so after it runs the program and gives the error, the focus to be automaticly placed in the errors pane. And he should be able to move the focus to the code pane immediately. __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind