Hi Rod,
Yes, the handles clause is the only thing that catches the event and you
can list many events there if you want.
I had a situation once where I changed everything outside the IDE, names of
controls only, and when loading the IDE, it did not like that, so I changed
them back and did it all inside the text editor...
The editor is behaving a lot better now that I have shut off all the auto
display and hints and stuff, for Windoweyes acts like it is chasing down all
those displays and gets stuck. I think it wants everything to remain still I am
sure.
Now the text editor is better than using Word and it has a slight delay
when you make any modifications but only a slight delay.
In C++ I don't use the IDE at all but could. I write text code using
notepad and run/debug using the DOS prompt command window that is provided.
I read the documentation and got the needed program to call to compile to
an .exe and that is all I do. I changed the name of that program using a batch
file to call from the command window to make it easier with all needed switches
added. I just called it MakeX.bat
Maybe I will use that IDE now that I have the text editor behaving better
now.
So, got to get back to my project.
Thanks, Bruce
Sent: Tuesday, April 02, 2013 8:02 AM
Subject: Re: RodMasterVolumePresetRotator 2.0 Released! :)
Hi Bruce: When you change a control's name there may be several places within
the code including code not usually displayed where the original name is used
like during the initialization of the form.
When you change the name in the designer the IDE automatically goes through
your code and changes all occurances of that control's name so things stay in
sync.
You can change the name in the Properties Window and that will also propagate
the change throughout your code.
I forget off hand if you change the name of the class in the text editor in
the ide if the change ispropagated and I usually change the name in the
Properties Window.
One thing to watch out for is that if you change the name I have seen a
situation where while the name of the control is changed in the vb.net code
class for the control in the form but the event handler line is not changed but
just removed and the code didnt throw an error.
So:
Private Sub MyControl_TextBox_Click stays the same but the
clause "Handles MyControl.Click " is gone.
So when I change a controls name I check in the code-behind (the vb.net
code block for the form) to ensure the handles claus is there.
It doesnt seem to matter if the sub name MyControl_Click(xxx) is changed
during event handling for a control.
So that is just another little thing to watch out for when mucking with
changing a control's name.
Rick USA
