connect

[mickey]

Hi, I've this problem; I need to connect a signal to a SLOT of myMainForm...How to do this? What's the best way to do this? thanks

void myDialog::init() {
	myMainForm* myw; //how obtain this
	connect(buttonGroupLL, SIGNAL(clicked(int)), myw, SLOT(activeTab(int)));

void myDialog::init() {
	myMainForm* myw; //how obtain this
	connect(buttonGroupLL, SIGNAL(clicked(int)), myw, SLOT(activeTab(int)));

To copy to clipboard, switch view to plain text mode 

[wysota]

Keep a pointer to this widget as a member of the dialog class and initialise it in the constructor of a dialog. Alternatively, if the widget is a parent of the dialog, you can use parent() call to retrieve it.

[mickey]

sorry, the problem is that function init() is inside a dialog.ui.h (create from designer).....
it hasn't parent...(I think)

[mickey]

furthermore, I need that mydialog.ui.h can see the state button of myainForm and viceversa....

[wysota]

You won't be able to do it with .ui.h. You have to subclass and reimplement the constructor. Remember that using "ui.h" is deprecated and that it is only a hack to avoid the need to subclass in common situations.

[mickey]

sorry,
1. why is it deprecated?
2.is it right create a dialog.ui.h from designer (leave that file empty) and sublcass it (and write code only here). Or which is the right way? thanks a lot

[zlatko]

You dont must create any *.ui.h files ! Actually Wysota explaine you upper why
Now do this things :]
- create form in Designer, set his name as FormBase and save it ;
- add this form to your project and create class Form that will be inherit your FormBase;
- use all members of FormBase in your Form class;

Have you understand

[mickey]

no I haven't understand. In designer if I create a form(dialog?), when I save it, its extension is .ui! How don't create .ui???

[zlatko]

You dont must create ui.h

[mickey]

if I save dialog from designer automatically a .ui.h is created.....

[wysota]

No. ui.h files are created when you enter some code into the form. And you're first asked if you want one to be created for you.

Anyway, that's all not the point. You can use .ui.h files if you insist to, but you need to subclass the class created by designer+uic anyway.

[mickey]

Keep a pointer to this widget as a member of the dialog class and initialise it in the constructor of a dialog.

yes, I made this.

myMainForm* _myw;
 
myLightDialog::myLightDialog( QWidget* parent, const char* name, bool modal, WFlags fl )
	:lightDialog (parent, name, modal, fl), _myw ( ????)( {
}

myMainForm* _myw;

myLightDialog::myLightDialog( QWidget* parent, const char* name, bool modal, WFlags fl )
	:lightDialog (parent, name, modal, fl), _myw ( ????)( {
}

To copy to clipboard, switch view to plain text mode 

Actually mymainForm isn't parent of myLightDialog...

[wysota]

So pass a pointer to it in the constructor.

You are posting in Qt programming section of the forum, I assume you know C++ basics, don't you? This issue doesn't have anything to do with Qt. It's a simple C++ issue of storing a pointer to an object as a class member.