Problem displaying my main window

[wysota]

Read and understand the chapter. We can give you the exact code for your problem but then you won't learn anything and you'll come right back with a simmilar issue.

[Salazaar]

But in book, there appear one more line after QApplication app... It's

Ui::MainWindow ui

Ui::MainWindow ui

To copy to clipboard, switch view to plain text mode 

which not appear in my application, but it works.

[Salazaar]

Hi than. I read chapter 2, I understand it, but I still don't know how to connect action to another dialog. It shows how to make slots and use it, but not how to connect two different dialogs. Regards

[jacek]

but not how to connect two different dialogs.

What do you mean by "connect two different dialogs"? Do you want to connect a signal from one dialog to a slot in the other one?

[Salazaar]

I want to connect action in my menu called actionAbout to dialog which is in ui_about

[jacek]

I want to connect action in my menu called actionAbout to dialog which is in ui_about

Define "connect". What exactly you want to happen?

[Salazaar]

if a ucer clicks a button, than about dialog is displayed

[jacek]

if a ucer clicks a button, than about dialog is displayed

I've already shown you how to do it.

Have you read the third chapter?

[Salazaar]

Right

void MainWindow::on_actionAbout_triggered()
 
      {
 
         OtherDialog dlg( this );
 
         dlg.exec();
 
      }

void MainWindow::on_actionAbout_triggered()
  
      {
  
         OtherDialog dlg( this );
   
         dlg.exec();

      }

To copy to clipboard, switch view to plain text mode 

And if I have a dialog included to my file called Dialog, so the OtherDialog will the replaced by Dialog? And what about "dlg"? and must on_aboutAction_triggered() be defined in slots section? I mean the same way that I do it with other functions?

[jacek]

And if I have a dialog included to my file called Dialog, so the OtherDialog will the replaced by Dialog?

Yes, you have to replace it with the name of a class you want to use.

And what about "dlg"?

It doesn't matter, it's just a variable.

and must on_aboutAction_triggered() be defined in slots section?

Yes, it has to be a slot.

As a homework, please, get a copy of C++ Primer (Polish edition is called Podstawy języka C++) by S. Lippman and J. Lajoie and read parts 2--5.

[Salazaar]

And to connect dialog to a slot, I have to do this, what is described in posts #65, 66
and also include this ui_about.h dialog file and nothing else? Will it be done correctly?

[wysota]

You don't connect a dialog to a slot. You connect a signal triggered() of the action actionAbout to a slot that has code which creates the dialog object and calls exec() on it to show it as modal.