Managed C++/CLI

Re: Updating form controls outside of form file

14-Mar-09 16:28

Lavake wrote:
But this doesn't work.

Because controls will be declared as private by default. Changing it to public and exposing to outside of the class is not recommended.

Lavake wrote:
For example, a function (outside the form header file) should be able to update a textfield in the form, during its execution. What would be the best way to do this in C++?

Best way is to write a delegate in your class. Let the form subscribe to it and update automatically when delegate is called. If you can't go with delegates, create a public method which updates the required controls on your form. Call this method from the outside function. Ofcource, you need to include the form's header file and your calling function should get an instance of the form.

Smile | :)

Navaneeth

How to use google | Ask smart questions

Lavake15-Mar-09 4:06

Lavake

15-Mar-09 4:06

Thanks for the help!

Ok so instead of declaring the control as public, I made a public method to update the control, but this doesn't really fix my problem...

MainForm^ mainform = gcnew MainForm();
Application::Run(mainform);
mainform->addUpdates("test");

The above code has the same effect as with mainform->txtUpdates->Text = "test";.
When I run my application no errors are reported, but the textbox "txtUpdates" isn't changed. I don't understand why not.

Re: Updating form controls outside of form file

N a v a n e e t h15-Mar-09 5:21

Problem to communicate between forms [modified]

15-Mar-09 5:21

Lavake wrote:
MainForm^ mainform = gcnew MainForm();
Application::Run(mainform);
mainform->addUpdates("test");

That's wrong. Application::Run blocks until the application exits. So mainform->addUpdates("test") will execute only when the application quits and you will not see the updates. For Application::Run, MSDN says,

The Dispose method of the Form class will be called prior to the return of this method.

Which means, mainform will be disposed before you call mainform->addUpdates("test"). To solve this, you need to rework on your design.

Smile | :)

Navaneeth

How to use google | Ask smart questions

roshihans14-Mar-09 3:44

14-Mar-09 3:44

Hi,

I have a problem to pass some data between forms. Let's say I have 2 form, FormMain and FormChild, FormChild will be called from FormMain. What I want to do is simple. Whenever I change the textBox1's text in FormChild, the textBox1's text in FormMain will also contain the same text. After googling for a while, I got 2 solution : by using a delegate or directly instantiate FormMain in FormChild. Both solution unfortunately is in C#, so I need to convert it first. Well, I thought at first that there will be no problem at all to convert it, but that is just plain wrong. Both of the solution I get is just give me some error. Here is the converted source code

1.using delegate

in Form Main.h :

#include "Form Child.h"

namespace Delegates {


	public delegate void AddTextChangeDelegate(String^ item);
	
	public ref class FormMain : System::Windows::Forms::Form
	{
	public:
		FormMain()
		{
			formChild = gcnew FormChild();
		}

	// declare as global variable	
	private:
		FormChild^ formChild;

	private: 
		System::Void button1_Click(System::Object^  sender, System::EventArgs^  e)
		{			
			formChild->AddTextChangeCallback = gcnew AddTextChangeDelegate(&this->AddTextChangeCallbackFn);
			formChild->Show();
		}

	private:
		System::Void AddTextChangeCallbackFn(String^ str)
		{
			textBox1->Text = str;
		}
	};
}

in Form Child.h

namespace Delegates {
	
	public ref class FormChild : System::Windows::Forms::Form
	{
	// declaring delegate, and get "error C2143: syntax error : missing ';' before '^' "
	// the compiler seems doesn't recognize this
	public:
		AddTextChangeDelegate^ AddTextChangeCallback;
	
	// user click add button and the delegate executed
	private:
		System::Void btnAdd_Click(System::Object^ sender, System::EventArgs^ e)
		{
			AddTextChangeCallback(textBox1->Text );
		}
	
	};
}

2. directly instantiate FormMain

the solution I get (in C#) is just simply declare FormMain as a global variable in FormChild, then exposed the textBox in FormMain as a public. But when I do the same thing in C++, the compiler give an error "error C2143: syntax error : missing ';' before '^' ". so probably I just need to include the Form Main.h in Form Child.h, which give me another error "fatal error C1014: too many include files : depth = 1024" (is it because both form include each other's header?, so that is like making some cyclic dependency thing? I'm not sure why). After googling once more, I found that it is still "possible" to declare FormMain instance in Form Child.h. Include Form Main.h in the Form Child.cpp and that's it.

in Form Child.cpp

#include "StdAfx.h"
#include "Form Child.h"
#include "Form Main.h"

System::Void FormChild::btnAdd_Click(System::Object^ sender, System::EventArgs^ e)
{
	
	FormMain^ formMain = gcnew FormMain();
	formMain->textBox1->Text = this->textBox1->Text;
	// I also have change it to this but the FormMain textBox1's text doesn't change
	// FormMain formMain;
	// formMain.textBox1->Text = this->textBox1->Text;
	// this will give memory access error in the runtime
	// FormMain^ formMain;
	// formMain->textBox1->Text = this->textBox1->Text;
}

But then another problem comes out. The instance declared in Form Child.cpp is not the same instance as the previous FormMain. So, what is the correct way to solve this problem? Is the methods mentioned above was wrong? Or perhaps I make a wrong conversion, misplaced the delegate or something? I have search the other solutions in the internet, but a lot of it is either in C# or VB. I could not find it for C++ .NET.
Also is there any way around to access the instance of FormMain from FormChild in the above case?

Thanks

N a v a n e e t h14-Mar-09 6:00

14-Mar-09 6:00

roshihans wrote:
But then another problem comes out. The instance declared in Form Child.cpp is not the same instance as the previous FormMain

Because you are instantiating a new instance in the child form. You need to pass the main form's instance to child form (through constructor injection or some setter methods).

roshihans wrote:
So, what is the correct way to solve this problem?

I will stick with delegates. It is the best way to go.

roshihans wrote:
AddTextChangeCallback(textBox1->Text );

Don't call it blindly, your delegate instance may be NULL and you will end with null reference exception. Do a sanity check before you call it.

System::Void btnAdd_Click(System::Object^ sender, System::EventArgs^ e)
{
    if(AddTextChangeCallback != nullptr)
        AddTextChangeCallback(textBox1->Text ); // Safe to call it now
}

roshihans wrote:
// declaring delegate, and get "error C2143: syntax error : missing ';' before '^' "
// the compiler seems doesn't recognize this

You might be doing it wrongly.

public ref class FormChild : System::Windows::Forms::Form
{
   public:
        delegate void AddTextChangeDelegate();
	AddTextChangeDelegate^ AddTextChangeCallback;
	
        ...........

};

Navaneeth

How to use google | Ask smart questions

roshihans14-Mar-09 16:08

14-Mar-09 16:08

Thanks for your quick reply, Navaneeth!! And now, the delegate thing is works perfectly!! I has been searching a lot about this in the internet without a result and now it's solved! Thanks a lot Navaneeth!! Thumbs Up | :thumbsup:

I dunno if my question is beyond the topic, but can I ask about another thing? this is about the answers that Navaneeth wrote

N a v a n e e t h wrote:
Because you are instantiating a new instance in the child form. You need to pass the main form's instance to child form (through constructor injection or some setter methods).

constructor injection? I'm still a beginner in C++, so I'm barely hear about this. When you say constructor injection, is it something like dependency injection? I'm googling it in the internet, and this is that came up. Correct me if I was wrong, but from what I read in Internet, this dependency injection can be done using a container (??), created by third party developer (they mentioned something about pico container and others). It can not be done by .NET itself? I'm still confused Confused | :confused:

N a v a n e e t h14-Mar-09 16:21

14-Mar-09 16:21

roshihans wrote:
constructor injection?

By constructor injection, I meant to pass the first form's object to second form via constructor. Something like

Form2(Form1^ form1) // First form's object is injected through constructor
{
    // keep the form1 object for future use
}

As I said, go with delegates. It's the approaprite solution for your scenario.

Smile | :)

Navaneeth

How to use google | Ask smart questions

roshihans14-Mar-09 17:33

14-Mar-09 17:33

N a v a n e e t h wrote:
By constructor injection, I meant to pass the first form's object to second form via constructor. Something like
Form2(Form1^ form1) // First form's object is injected through constructor
{
    // keep the form1 object for future use
}

But Form1 already include Form2.h (in my case Form1 act as a "parent" form, and instantiate Form2). So I think I can't declare Form2 (Form1^ form1) and keep the form1 object, like you have mentioned above, because I need to include Form1.h inside Form2.h, and that will give me this "fatal error C1014: too many include files : depth = 1024". Or maybe I don't need to include Form1.h inside Form2.h?

Thanks

N a v a n e e t h15-Mar-09 5:14

15-Mar-09 5:14

roshihans wrote:
But Form1 already include Form2.h (in my case Form1 act as a "parent" form, and instantiate Form2). So I think I can't declare Form2 (Form1^ form1) and keep the form1 object, like you have mentioned above

Fair point! You will get circular dependency problems. To solve this, you need to have good understanding about C++ compiling and linking.

You have to use forward declaration and declare parent form in child form's header file. Assume your parent form is named as PForm and child form as CForm. Here is how your PForm's header file looks like

public ref class PForm : public System::Windows::Forms::Form{
public:
    void UpdateText(String^ str) // used to update the text box text. This will be called from CForm.
    {
	textBox1->Text = str;
    }

    // your rest of code
};

Here is your CForm's header

ref class PForm; // forward declaring PForm

public ref class CForm : public System::Windows::Forms::Form{
public:
    CForm(PForm^ pf) // injecting dependency through constructor
    {
	InitializeComponent();
	pForm = pf;
    }

private: 
    System::Void textBox1_TextChanged(System::Object^, System::EventArgs^);
    PForm^ pForm; // Parent form's object used to update the control
};

CForm.cpp contains

#include "CForm.h"
#include "PForm.h"

System::Void CForm::textBox1_TextChanged(System::Object ^sender, System::EventArgs ^e){
	if(pForm != nullptr)
		pForm->UpdateText(textBox1->Text);
}

You show the CForm from PForm like

CForm^ cForm = gcnew CForm(this);
cForm->Show();

This should work fine. But if you use delegates, you can avoid all these and implementation will be pretty straight forward. So please stick with delegates unless you have a good reason to go with the above method.

Hope it is clear now. Smile | :)

Navaneeth

How to use google | Ask smart questions

roshihans15-Mar-09 18:12