Dialog opens twice

[ulmly]

Hi !

If user clicked a button then a dialog will pop up.

The problem is that the dialog pops up twice, one after another. That means, after user give an input and click OK, the same dialog appears and asks user again.

However, other buttons which do open the same dialog have no such a problem.

The dialog class inherits QDialog.

Does converting to Qt4 play role in this case ? Because the problem button is already located on ui file which has been converted through Qt4's designer and the other buttons are still on Qt3's ui files.

Thx in advance.

[wagmare]

show us the code snippet : how u are poping the new dialog ..

[ulmly]

On the problem button (defined in cpp file):

void
SensitivitiesWidget::on_SingleFunctionChooser_clicked()
{
  const CCopasiObject * pObject =
    CCopasiSelectionDialog::getObjectSingle(this,
              CCopasiSimpleSelectionTree::NumericValues);
}

void
SensitivitiesWidget::on_SingleFunctionChooser_clicked()
{
  const CCopasiObject * pObject =
    CCopasiSelectionDialog::getObjectSingle(this,
              CCopasiSimpleSelectionTree::NumericValues);
}

To copy to clipboard, switch view to plain text mode 

On one of other buttons (defined in ui.h file):

void Curve2DWidget::buttonPressedX()
{
  if (!mpModel) return;
 
  mpObjectX = CCopasiSelectionDialog::getObjectSingle(this,
              CCopasiSimpleSelectionTree::NumericValues);
}

void Curve2DWidget::buttonPressedX()
{
  if (!mpModel) return;

  mpObjectX = CCopasiSelectionDialog::getObjectSingle(this,
              CCopasiSimpleSelectionTree::NumericValues);
}

To copy to clipboard, switch view to plain text mode 

[ulmly]

If I go back to the old Qt3's ui file, the problem does not come up.

I believe this is about converting problem to Qt4.

However, I did do some works on interface only in converting progress

[ulmly]

No, the problem does not really correlated to converting process.

If I changed the name of button, the problem will disappear. The window will pop up once.

However, I don't still understand why changing the button name simply solve the problem. I have checked whether the name is used somewhere else in the code, but everything looks like OK.

Any idea ???

[wysota]

Do you have a connect() statement related to the on_SingleFunctionChooser_clicked() slot?

[ulmly]

Yes, I have.

The connect() statement is automatically generated from SensitivitiesWidget.ui file. That means it is in ui_SensitivitiesWidget.h.

The slot itself has been declared in SensitivitiesWidget.h and defined in SensitivitiesWidget.cpp.

[wysota]

Then you have two connections to the same slot. If you name a slot in a form of on_objectName_signalSignature() it will be automatically connected to the signalSignature() signal from objectName. Either remove the connection in Designer or change the slot name.

[ulmly]

Aha ! I see !

The on_objectName_signalSignature() slot is automatically connected to the signalSignature() signal from objectName. This is done by default. Also, I should not spend an extra effort to make signal-slot connection, even in Qt Designer. Just declare it in header file and define in implementation one.

However, why am I not able to see the 'second' connect() statement ? Is the statement hidden from us ?

[wysota]

The on_objectName_signalSignature() slot is automatically connected to the signalSignature() signal from objectName. This is done by default. Also, I should not spend an extra effort to make signal-slot connection, even in Qt Designer. Just declare it in header file and define in implementation one.

It's better to make the connection graphically and name the slot in a way that it gives more information about what it does instead of a vague information when it is triggered.

However, why am I not able to see the 'second' connect() statement ? Is the statement hidden from us ?

The second connection is done by
QMetaObject::connectSlotsByName() that is called from setupUi() in the file generated by uic from your Designer form.