Creating a Main Window Application

[gt.beta2]

Hello,

I've been reading this example: http://doc.trolltech.com/4.4/mainwin...plication.html.

What if i wanted to use Qt Designer with Qt Creator MainWindow template!

When we go to Project > Qt4 GUI Application > create a MainWindow project we get some thing like this:

main.cpp

#include <QtGui/QApplication>
#include "mainwindow.h"
 
int main(int argc, char *argv[])
{
    QApplication a(argc, argv);
    MainWindow w;
    w.show();
    return a.exec();
}

#include <QtGui/QApplication>
#include "mainwindow.h"

int main(int argc, char *argv[])
{
    QApplication a(argc, argv);
    MainWindow w;
    w.show();
    return a.exec();
}

To copy to clipboard, switch view to plain text mode 

mainwindow.h

#ifndef MAINWINDOW_H
#define MAINWINDOW_H
 
#include <QtGui/QMainWindow>
 
namespace Ui
{
    class MainWindowClass;
}
 
class MainWindow : public QMainWindow
{
    Q_OBJECT
 
public:
    MainWindow(QWidget *parent = 0);
    ~MainWindow();
 
private:
    Ui::MainWindowClass *ui;
};
 
#endif // MAINWINDOW_H

#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <QtGui/QMainWindow>

namespace Ui
{
    class MainWindowClass;
}

class MainWindow : public QMainWindow
{
    Q_OBJECT

public:
    MainWindow(QWidget *parent = 0);
    ~MainWindow();

private:
    Ui::MainWindowClass *ui;
};

#endif // MAINWINDOW_H

To copy to clipboard, switch view to plain text mode 

mainwindow.cpp

#include "mainwindow.h"
#include "ui_mainwindow.h"
 
MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent), ui(new Ui::MainWindowClass)
{
    ui->setupUi(this);
}
 
MainWindow::~MainWindow()
{
    delete ui;
}

#include "mainwindow.h"
#include "ui_mainwindow.h"

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent), ui(new Ui::MainWindowClass)
{
    ui->setupUi(this);
}

MainWindow::~MainWindow()
{
    delete ui;
}

To copy to clipboard, switch view to plain text mode 

If now i want to reuse the code of the example without the Qt Designer ... where showld i start?!
Guess this is a more complex inheritance scheme ... but i would like to use it.

Thaks for the more patient ones

[gt.beta2]

found this ...
http://doc.trolltech.com/qtcreator-0...g-program.html

Looks like a starting point.

[wysota]

Let's make one thing straight. A "main window" is by no means different than a "regular" window/dialog/widget. It just has additional capabilities in regards to what is inside the window, so everything that applies to a "regular" widget, applies to a "main window" widget as well.

Designer reads and writes UI files that have a .ui extension. Now try guessing which files from the ones created by Creator or whatever else tool anyone might have been using might be opened with Designer.

Have you read the "Using Forms and Components" section of Designer docs or did you only have a glimpse of it? If the latter then go back and read with understanding what is written there. All your questions can be answered just by reading and understanding the first part of that section of documentation.

[stevey]

When I started on Qt, I found that I didn't need to stray any further than the Qt Assistant doco to learn how things work. You need to spend time reading the doco, it's VERY important. Work through the tutorials contained in the doco as well.

[gt.beta2]

Yes ... you are right.
I was in "kind of a hurry" but i guess i definitely need some reading
Thanks all .... "I'll be back"

[gt.beta2]

Ok then.

I've been trough the The Direct Approach, The Single Inheritance Approach and The Multiple Inheritance Approach.

Guess that each one as it's own application filed.

The third one seems more comfortable to use, although it says that "...but does not conveniently support composition of multiple user interfaces".

When i use Qt Creator to start a project based on QDialog class (for instance) it uses single inheritance ... right!

Can i ask why? Is it because of what i said above, and this way the template will cover all situations?

Hope this is not another stupid question

[wysota]

Can i ask why?

Because if they chose multiple inheritance, you could have asked the same question

Probably the person who was writing this piece of code preferrs single over multiple inheritance.