Window-Eyes 8.0: New Features Webinar Recording Now Available for Download!HI
Bruce: Last assignment for the day, I promise - I think.
Next lets set up form1 and add a button and textBox:
Open vb.net and open TestProject.
Hit ctrl+alt+l to ensure the SolutionExplorer is open.
Now navigate to Form1.vb and hit enter on it to open the Forms Designer.
In a few seconds hit
f4 to open the properties window:
We need to give our form some size or you will encounter problems adding and
working with controls so...
tab around to the list of properties.
They should be the first tab after the ToolBar.
Lets put the list of properties in alphabetical order so they are easier to
follow...
Tab back to the ToolBar, right arrow to Alphebetical button and click it.
If you are not placed in the list of properties tab to it.
Arrowdown to the Font property and right arrow to open it.
Arrow down to the
"Size" property, tab to the textbox and set it to something reasonable like 14
Then backtab and down arrow to the Unit property and tab to the browse button
and click it.
Up arrow to Pixel and hit enter on it.
Next Arrow down to the "Size" property
Tab to get into the TextBox and set the size
1000, 700
Then tab back to the properties list.
The first number, 1000 is the horizontal extent and the 700 is the vertical
extent of our form now.
and it is in pixels so we can figure out how things will fit on our form.
Hit F4 to close the Properties Window and return to FormsDesigner.
Now drop a TextBox on the form, hit f4 and set the following properties
Arrow down to Location and set it to say 50, 100
Arrow to the Size Property and set it to something like 200, note just leave
whatever size is set by the compiler for the vertical size for now).
If you want some default text arrow down to the Text property and type
something in that TextBox like Initial Value or whatever.
Note to set the Properties Window to a tabbed document under the Window menu
then
Hit ctrl+f4 to close the Properties Window and get back to Forms Designer.
Open the ToolBox and drop a Button on the form ( just click the button option
in the ToolBox list of controls).
Hit F4 to open the properties Window.
Arrow Down to the Location Property and set it at say 800, 650
Then arrow down to the Text Property and set it to something like Click Me
Then back tab to the ToolBar and right arrow to the Events button and click it.
Click the Click event and you are placed in the Code Editor.
Enter:
TextBox1.Text = "Hay, it worked"
Then ctrl+f4 and save the changes until you are back into Solution Explorer.
Now go to the top of Solution explorer and hit ctrl+f5 to run the project.
You should be able to tab between the button and the TextBox seeing any default
text you put in the TextBox while in the Properties Window.
If you click the button
You will see the new text in the Textbox.
OK, phew, if you get this far we are ready to continue testing with a form and
controls we know all fit together, the form is big enough to hold the controls
and they are located well within the form and the Code-Behind file is wired up
and working.
Let me know when you get this far and let me know if you run into anything at
all that slows you down.
Dont forget:
Set all windows to TabbedDocuments under the Windows Menu if you can.
Also the ToolBox has some categories of controls so you can open and close some
of the items in the ToolBox with the right and left arrow keys to make working
with it much faster.
Has the Code Editor performance improved? There are several other option
changes we will look at that should also help things but this is enough for
today.
Rick USA
----- Original Message -----
From: RicksPlace
To: [email protected]
Sent: Tuesday, February 12, 2013 9:16 AM
Subject: Re: Visual Basic 2010 Event List and Window
Hi Bruce:
Next open vb.net and click the OptionsMenuItem under the ToolsMenu.
Just left arrow to close everything until you hear the Environment Branch.
This is a TreeView of Tabbed Documents.
Tab until you hear Show All Items and check it.
Then tab back to the Environment branch and right arrow to open it.
Arrow down if necessary to the General Tab of the Environment Branch.
Uncheckautomatically adjust visual environment checkbox,
Tab andunchecked enable visual experience rich client experience checkbox,
Uncheck use hardware acceleration,
close button effects active window only is checked,
Autohide effects active window is unchecked,
Then tab to the ok button and click it.
Now close the ide, open it and try typing something in the code editor for
Form1.vb.
Just type comments for now like:
' This is a test line.
' This is another
See if the typing has improved yet.
You can save the project by hitting alt+f4 and just saving the project
without specifying anything this time.
Let me know if these changes had any effect.
They likely will not have but they are the place to start.
Rick USA
----- Original Message -----
From: RicksPlace
To: [email protected]
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
