Qt show modal dialog (.ui) on menu item click

[tomorrow]

void MainWindow::get_started_info()
{
    QMessageBox::information(this,"About","message");// dont forget to include QMessageBox
}

void MainWindow::get_started_info()
{
    QMessageBox::information(this,"About","message");// dont forget to include QMessageBox
}

To copy to clipboard, switch view to plain text mode 

this works, when I click on Get Started, this message box appears

get_started *one; //in your mainwindow under private

get_started *one; //in your mainwindow under private

To copy to clipboard, switch view to plain text mode 

like this :

private:
    Ui::MainWindow *ui;
    //! Create the menu classes
    void createActions();
    void createMenus();
    //! Menu Items
    QMenu   *home;
    QMenu   *help;
    QAction *quit;
    QAction *start;
    QAction *about;
    get_started *one;

private:
    Ui::MainWindow *ui;
    //! Create the menu classes
    void createActions();
    void createMenus();
    //! Menu Items
    QMenu   *home;
    QMenu   *help;
    QAction *quit;
    QAction *start;
    QAction *about;
    get_started *one;

To copy to clipboard, switch view to plain text mode 

but I get an error 'get_started' does not name a type

[toufic.dbouk]

but I get an error 'get_started' does not name a type

Did you include get_started.h ?
And you have

#include "ui_get_started.h"

#include "ui_get_started.h"

To copy to clipboard, switch view to plain text mode 

I am not sure if you need this to be included in both header and cpp file, maybe just in your .cpp file.

Good Luck.

[anda_skoa]

The original code was almost correct, the only mistake was usign qApp as the receiver object instead of this.

Creating the dialog on the stack and excuting it as a modal dialog using exec() where correct.

Cheers,
_

[toufic.dbouk]

Creating the dialog on the stack and excuting it as a modal dialog using exec() where correct.

Yes it was correct and we mentioned that he can keep his code since its right instead of creating it on heap. Creating it on the stack will limit the scope where you can use the object for further usage.