How to enable a button in a child form from another child form without creating a new instance

Question

0.00/5 (No votes)

See more:

Hello codeproject I have an mdi app with menustrip that has two drop down items one of the drop down item links to a form lets say form2.i also have a login form ,i want that whenever a user logs in with a particular role , a button in the form2 should be enabled witout creating a new instance of the form2. But if you click on the form2 menustripitem you should noticed that the button in the form2 haz bin enabled

thanks evryone for your help.

Posted 1-Sep-12 19:51pm

Ese ochuko

Add a Solution

1 solution

Add a Solution

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)

OriginalGriff · Answer 1 · 2012-09-01T20:14:00

Solution 1

The best way to handle this is via the MDI Parent.

Your login form (assuming it is a MDI Child) should create an event, which the parent handles: LoginStatusChanged for example.
The parent then reads the login information from the login form via one or more public properties and passes it as necessary to the other MDI children, again via public properties.

Each individual child then looks at the new status when the property changes and sets it's menus, tool bars, and other controls to the appropriate state.

The advantage of this approach is that no form needs to know about the existence of the others (except the parent, but since it creates the children, that's allowed)

If you don't know how to do any particular part of this, just ask!

Posted 1-Sep-12 20:14pm

OriginalGriff

Comments

Ese ochuko 2-Sep-12 9:26am

Thank u vry much for your reply but can u please can you show me sme example with codes thanks very much for your response

OriginalGriff 2-Sep-12 10:15am

For which bit? :laugh:
Remember I have no idea of your skill level, but also I don't want to patronise you or do extra, unnecessary work myself!

Ese ochuko 3-Sep-12 2:29am

Am a beginner ,i think i need every bit, laugh. Even if u wana add screen shot thats okay by me .thanks very much

OriginalGriff 3-Sep-12 3:17am

Adding an event is easy: the complete code is at the top of this tip: http://www.codeproject.com/Tips/400287/A-simple-code-snippet-to-add-an-event
(The rest of the tip just makes it easier to add them in VS). To signal the event to the parent, the child form just calls the OnXxxxx routine (OnFilterChange in the example).

Properties are also easy:
public MyProperty { get; set; }
is a complete automatic property, but you can put what code you like in the getter and setter:
public MyOtherProperty
{
get { return myTextBoxWithUserName.Text; }
set
{
myTextBoxWithUserName.Text = value;
if (value == "Not a valid user name")
{
MessageBox.Show("Then why are you setting it?");
}
}
}