G
glenn
I have a very serious problem with my forms and components that I was
wondering if there was a way to turn off. The problem is as follows:
1) create a form and place 50 components on the form with various types of
events attached to each field and grid, such as exit events, key press
events and so on.
2) Deside at some point that you made a mistake and need to have a tabbed
notebook on the form to help break down the clutter and organize
information.
3) Cut all fields from form, drop tabbed notebook down and then paste all
fields back onto the form and let the fun begin.
What happens at this point is all of the fields are pasted back to the form,
except now they have no events attached to them. This is a very serious
problem but for some reason the developers of VS desided to make it worse.
If you decide you would like to relink that exit event for textbox1 and you
go double click on it, instead of linking to the event that has already been
created and has that name associated with it, the sytsem will instead create
a -2 version of the same event and link it to somewhere that has no code
what so ever.
I am looking at starting a new project in VS that is going to become a very
large project with a huge user interface component. However, this one issue
is causing me serious concern as to whether VS is ready for such a
production use. I know there are millions of other programmers using it to
create applications, however, they are a lot more willing to deal with this
stuff that we are. I am wondering if there is some property some where that
can be changed that would cause the environment to link back properly or at
the very least not create more events when an event already exists with that
fields name.
Thanks,
glenn
wondering if there was a way to turn off. The problem is as follows:
1) create a form and place 50 components on the form with various types of
events attached to each field and grid, such as exit events, key press
events and so on.
2) Deside at some point that you made a mistake and need to have a tabbed
notebook on the form to help break down the clutter and organize
information.
3) Cut all fields from form, drop tabbed notebook down and then paste all
fields back onto the form and let the fun begin.
What happens at this point is all of the fields are pasted back to the form,
except now they have no events attached to them. This is a very serious
problem but for some reason the developers of VS desided to make it worse.
If you decide you would like to relink that exit event for textbox1 and you
go double click on it, instead of linking to the event that has already been
created and has that name associated with it, the sytsem will instead create
a -2 version of the same event and link it to somewhere that has no code
what so ever.
I am looking at starting a new project in VS that is going to become a very
large project with a huge user interface component. However, this one issue
is causing me serious concern as to whether VS is ready for such a
production use. I know there are millions of other programmers using it to
create applications, however, they are a lot more willing to deal with this
stuff that we are. I am wondering if there is some property some where that
can be changed that would cause the environment to link back properly or at
the very least not create more events when an event already exists with that
fields name.
Thanks,
glenn
