By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,948 Members | 1,559 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,948 IT Pros & Developers. It's quick & easy.

Form Inheritance

P: n/a
Joe
Hello,

I created a base form with a few textbox and button controls on
it. I then created a child form from this base form using the Add
Item process in Visual Studio 2005.

Problem: All of my controls on the child form are locked and
I cannot seem to unlock them.

Anyone know how I can create a child form where the controls
are NOT locked or else unlock the controls after the child form has
been created?
J
Feb 28 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
What do you mean by "locked"? They are inherited, and their position, size
and so on are set in the base controls InitializeComponent() event, so you
can't modify them from the derived control. You would have problems if this
was allowed, since two controls could try to "reconfigure" the base's controls.
Hello,

I created a base form with a few textbox and button controls on
it. I then created a child form from this base form using the Add
Item process in Visual Studio 2005.

Problem: All of my controls on the child form are locked and
I cannot seem to unlock them.

Anyone know how I can create a child form where the controls
are NOT locked or else unlock the controls after the child form has
been created?

J

Feb 28 '08 #2

P: n/a
Joe,

As you use verbs which has no meaning, you seldom get an answer here or it
should be your goal to get a long line of not understand answers and
replies.

Locked has not any meaning here it can be not enabled, not visible, read
only etc..

Cor

Feb 29 '08 #3

P: n/a


"Jack Jackson" wrote:
On Fri, 29 Feb 2008 06:25:50 +0100, "Cor Ligthert[MVP]"
<no************@planet.nlwrote:
Joe,

As you use verbs which has no meaning, you seldom get an answer here or it
should be your goal to get a long line of not understand answers and
replies.

Locked has not any meaning here it can be not enabled, not visible, read
only etc..

Cor

Actually I think "locked" is not a bad word since when you click on
one of those items in the designer you see a little locked padlock on
the item.
Yeah. And Cor: those are technically adjectives. I guess you could argue
that "enabled" and "locked" are verb participles or something nerdy like
that, but you mentioned "visible" which is clearly an adjective. I understand
your basic point but you don't have to be a jerk about it.

Or does Microsoft formally require that now?
Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.