Non-visual inheritance for Form?

[James Ramaley]

In my application all forms have some non-visual behaviour implemented
with several methods. Normally, if this common functionality was not
form-related, I would just create a basic class and inherit everything
from it. However, inheriting the Form class involves "Visual
Inheritance" which I would like to avoid. I wouldn't like my common
Form class appear in the designer. Is there a way I can avoid this? Is
there another way I could implement common non-visual form
functionality?

thanks

[One Handed Man \( OHM - Terry Burns \)]

Sure, simpy create a form with no controls on it, implement your standard
code and inherit from this. You can add your own controls on the new form.
--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing

"James Ramaley" <jr******@iname.com> wrote in message
news:f8**************************@posting.google.c om...

In my application all forms have some non-visual behaviour implemented
with several methods. Normally, if this common functionality was not
form-related, I would just create a basic class and inherit everything
from it. However, inheriting the Form class involves "Visual
Inheritance" which I would like to avoid. I wouldn't like my common
Form class appear in the designer. Is there a way I can avoid this? Is
there another way I could implement common non-visual form
functionality?

thanks