multiple forms
-
Is the form1 parent of form2 ?
Koushik
-
kabutar wrote:
i dont want to use delegates....
Why not ? Delegates are the best way to do this, why are you setting out to write bad code ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillionOneHundredAndFortySevenMillionFourHundredAndEightyThreeThousandSixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it )
-
yes Koushik ..... form1 is the parent form and form2 is the child form.... when we click on a button in form1 the form2 will pop up..... :) thanks in advance...
C#
f you want to write nasty code, you can pass a reference to form1 in to form2. Again, why won't you use a delegate ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillionOneHundredAndFortySevenMillionFourHundredAndEightyThreeThousandSixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it )
-
yes Koushik ..... form1 is the parent form and form2 is the child form.... when we click on a button in form1 the form2 will pop up..... :) thanks in advance...
C#
Try with the following code...but i think its not recommended to do so as you are trying to pass the reference of the form object... replace form2 constructor as follows... private Form1 m_parent; public Form2 (Form1 parentForm) { InitializeComponent(); m_parent = parentForm; } Now declare a public method in your form1 to access the textbox1.text ..now in the form2 u will be able to access the form1's textbox text by using some thing like this.. m_parent.GetForm1Text() where GetForm1Text() gives you the text of the TexBox in form1
Koushik
-
f you want to write nasty code, you can pass a reference to form1 in to form2. Again, why won't you use a delegate ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillionOneHundredAndFortySevenMillionFourHundredAndEightyThreeThousandSixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it )
its something like this Christian.... i wrote it with delegates but i was not very clear withy certain things in the code or how they work.....because i got the code form google... so i wanted to try it again with and without trying delegates.... since u r insisting so much that its a bad practise i think i should stick with delegates and not waste my time the other way round... thanks Chris..
C#
-
its something like this Christian.... i wrote it with delegates but i was not very clear withy certain things in the code or how they work.....because i got the code form google... so i wanted to try it again with and without trying delegates.... since u r insisting so much that its a bad practise i think i should stick with delegates and not waste my time the other way round... thanks Chris..
C#
kabutar wrote:
because i got the code form google...
OK - in that case, I recommend you bookmark the MSDN site. If you find code that works for you via google, then you should read MSDN to learn how the various parts of that code work. Any source of info will do, but MSDN will give you exact definitions of the classes and methods you see being used. Delegates can be a little confusng at first, but once you get the hang of them, you'll find they are very useful.
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillionOneHundredAndFortySevenMillionFourHundredAndEightyThreeThousandSixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it )
-
its something like this Christian.... i wrote it with delegates but i was not very clear withy certain things in the code or how they work.....because i got the code form google... so i wanted to try it again with and without trying delegates.... since u r insisting so much that its a bad practise i think i should stick with delegates and not waste my time the other way round... thanks Chris..
C#
kabutar wrote:
i wrote it with delegates but i was not very clear withy certain things in the code or how they work.....because i got the code form google...
You should not use a code that is not fully understood. Check this example and try you can make it. I presume you created two forms say Form1 and Form2. You are going to declare delegate on Form2 as public. See the below code
public delegate void InformParent();
public InformParent ParentDelegate;ParentDelegateis an object for InformParent delegate. In this sample I have not passed any parameters. You can pass whatever values you want. Now check the below code to see how this can be invoked.Form2 frm = new Form2();
frm.ParentDelegate = new WindowsApplication1.Form2.InformParent(this.InformParent);
frm.Show();In this InformParent() is a private method for Form1. See below
private void InformParent()
{
//Do your form1 update code
}When delegate is invoked, this function will be called. When you want to inform the changes to Form1 from Form2, call
ParentDelegate(), which will call method in Form1. Hope this makes it clear
-
f you want to write nasty code, you can pass a reference to form1 in to form2. Again, why won't you use a delegate ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillionOneHundredAndFortySevenMillionFourHundredAndEightyThreeThousandSixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it )
Christian Graus wrote:
f you want to write nasty code
But how this will be nasty ? Delegates also we are passing the function reference, in this case we are passing object reference. What is the difference ?
-
kabutar wrote:
i wrote it with delegates but i was not very clear withy certain things in the code or how they work.....because i got the code form google...
You should not use a code that is not fully understood. Check this example and try you can make it. I presume you created two forms say Form1 and Form2. You are going to declare delegate on Form2 as public. See the below code
public delegate void InformParent();
public InformParent ParentDelegate;ParentDelegateis an object for InformParent delegate. In this sample I have not passed any parameters. You can pass whatever values you want. Now check the below code to see how this can be invoked.Form2 frm = new Form2();
frm.ParentDelegate = new WindowsApplication1.Form2.InformParent(this.InformParent);
frm.Show();In this InformParent() is a private method for Form1. See below
private void InformParent()
{
//Do your form1 update code
}When delegate is invoked, this function will be called. When you want to inform the changes to Form1 from Form2, call
ParentDelegate(), which will call method in Form1. Hope this makes it clear
-
frm.ParentDelegate = new WindowsApplication1.Form2.InformParent(this.InformParent); can you explain this code to me Navneeth.......especially this part.....new WindowsApplication1.Form2.InformParent(this.InformParent); thanks :)
C#
kabutar wrote:
frm.ParentDelegate = new WindowsApplication1.Form2.InformParent(this.InformParent);
It's nothing but initializing delegate and telling where it should call. So when you call
ParentDelegate()from Form2, it will call private methodInformParent()which is in Form1