Visual Inheritance in VB.NET

Question

1.00/5 (1 vote)

See more:

Hello All,

I have created a child form and I want to inherit this form on to the parent form. I did it using Visual Inheritance. On my parent form I can find glymphs of child form. My question is can I move, resize the controls of the child form being in the parent form. Please let me know how to do that.

Posted 5-Jan-12 23:59pm

Nara Har

Add a Solution

Comments

Sergey Alexandrovich Kryukov 6-Jan-12 6:02am

This is beyond good and evil. What is "being in the parent form"? What is "parent form", after all (parent-child relationships between forms are not functional)? How is this related to inheritance? I'm not even sure you have to answer. Better learn things a bit better to understand what to ask about.
--SA

Nara Har 6-Jan-12 6:20am

Need to get the replica of FormA onto FormB. I did this. But all the controls of FormA are locked when placed on FormB. Now I want to move them. Is it possible?

Dave Kreskowiak 6-Jan-12 14:54pm

No, it's not possible to move the controls. The point behind inheriting is to inherit the EXACT look of the parent. The only way to move the controls is to move them on the parent form.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)