Dynamic object's method.

Hi, I wrote code to generating simple form:

Code:

---

QDialog *dialogWindow = new QDialog(this);
dialogWindow->setWindowTitle("Adding text");
dialogWindow->setFixedSize(350, 200);
QGridLayout *layout = new QGridLayout(dialogWindow);
QPlainTextEdit *text = new QPlainTextEdit();
QDialogButtonBox *buttonBox = new QDialogButtonBox(dialogWindow);
buttonBox->addButton(QDialogButtonBox::Ok);
buttonBox->addButton(QDialogButtonBox::Cancel);
layout->addWidget(text);
layout->addWidget(buttonBox);
dialogWindow->setLayout(layout);
dialogWindow->connect(buttonBox, SIGNAL(accepted()), dialogWindow, SLOT(accept()));
dialogWindow->connect(buttonBox, SIGNAL(rejected()), dialogWindow, SLOT(reject()));

---

But, I didn't know how to write method onTextChanged to QPlainTextEdit object? Any ideas?

Sure, connect the QPlainTextEdit's textChanged() signal to a custom slot where you put your code. You should learn basics about signals and slots and widget applications first.

Yes, but I would like to do if QPlainTextEdit->toPlainText() return empty string, ok button is disabled else it is enabled. I can use signals and slots, but I didn't know how do that in this case.

In the slot connected to textChanged() that I mentioned in my previous post, call toPlainText().isEmpty() on your QPlainTextEdit to know whether its text is empty, then setEnabled() on the button as needed.

But to do that I need an additional method and two pointers to QPlainTextEdit and QPushButton, because I create a QDialog in the method of the main form, right? Otherwise can not be?

Indeed.

In any case, creating a form that way is not very common, best practise is to create a subclass of, in this case QDialog, and encapsulate all its internals into that class.

That way the user of the dialog/form only deals with the class' public API, independent on how it is actually implemented internally.

Cheers,
_

Ok, thanks.