views:

50

answers:

2

In Qt, what is the most elegant way to pass data from a QDialog subclass to the component that started the dialog in the cases where you need to pass down something more complex than a boolean or an integer return code?

I'm thinking emit a custom signal from the accept() slot but is there something else?

+1  A: 

QDialog has its own message loop and since it stops your application workflow, I usually use the following scheme:

MyQDialog dialog(this);
dialog.setFoo("blah blah blah");
if(dialog.exec() == QDialog::Accepted){
  // You can access everything you need in dialog object
  QString bar = dialog.getFoo();
}
tibur
This is true if the dialog is modal... In my case it was, but I was just thinking how would you do this in a non-modal dialog? I guess connect the dialog's accepted signal to a slot where you do the same stuff as above.
teukkam
So, no need to emit a custom signal from the `accept()` slot. The `connect` signal seems to be the appropriate one.
tibur
+1  A: 

In the general case, if the data is fairly simple I like to create one or more custom signals and emit those as necessary. Simple or complex data, I will generally provide accessors for the data. In the complex case, then, I would connect a slot to the accepted signal, and get the desired information in that slot. The drawback to this is that you generally need to rely on storing a pointer to the dialog, or using the sender() hack to figure out which object triggered the slot.

void Foo::showDialog()
{
    if ( !m_dlg )
    {
        m_dlg = new Dialog( this );
        connect( m_dlg, SIGNAL( accepted() ), SLOT( onDialogAccepted() ) );
    }
    m_dlg->Setup( m_bar, m_bat, m_baz );
    m_dlg->show();
}

void Foo::onDialogAccepted()
{
    m_bar = m_dlg->bar();
    m_bat = m_dlg->bat();
    m_baz = m_dlg->baz();
    // optionally destroy m_dlg here.
}
Caleb Huitt - cjhuitt