Application crashes at launch-time

[high_flyer]

I'll ask you once more, why my application doesn't have functionality?

We don't even know what functionality you are talking about.
Do you know how to use signals and slots?

[Salazaar]

We don't even know what functionality you are talking about.

Objects on which I was doing:

ui.element->hide();

ui.element->hide();

To copy to clipboard, switch view to plain text mode 

doesn't work, nextStepButton does nothing and so on. Maybe It'll b e better if you can see my code. I'll attach dialog.cpp

Do you know how to use signals and slots?

Your kidding me? Of course, I know.
edit:
The problem isn't that I don't know how to connect signals to slots, I have functions which do something, connected to something and all should work, but it doesn't. Look at my file

[high_flyer]

well, settingUp() is a bunch of if() clauses.
Probably none of them gets to be true, so nothing happens.
Put a debug statement in and see if its being printed:

bool Dialog::settingUp()
 {
     qDebug()<<"Dialog::settingUp()";
    //the rest of your code.
}

bool Dialog::settingUp()
 {
     qDebug()<<"Dialog::settingUp()";
    //the rest of your code.
}

To copy to clipboard, switch view to plain text mode 

In addition make sure you get no signal/slot warnings when you execute the application.

[Salazaar]

well, settingUp() is a bunch of if() clauses.
Probably none of them gets to be true, so nothing happens.

None?? If I, let's say' check checkbox in one group, and second in second grop and if nextStep Button is clicked one if() clause sure returns true and all instructions in if() should be done. But even if is a problem (which I think it isn't a problem) some widgets should be hidden, and we can type any value (even string) to lineEdit, although I have a validator.

In addition make sure you get no signal/slot warnings when you execute the application.

No, I don't have any signal/slots warning when executing application.

[high_flyer]

did you try the code I gave you in the last post?

[Salazaar]

Yes, I tried it, application compiled with no errors, and no errors at launching.

[high_flyer]

Amm... yes, I expected as much, but the point was to see if you ar getting the debug message...

EDIT:
you should start the application from the console

[Salazaar]

Debug message? What do you mean? I tried to type make all instead of make, and reached message that it cannot find file somename.dll. And if it's not the answer you were expecting, how can I reach debugg message?

[high_flyer]

Am... look at the code I gave you.
there is a line:

qDebug()<<"Dialog::settingUp()";

qDebug()<<"Dialog::settingUp()";

To copy to clipboard, switch view to plain text mode 

This will print 'Dialog::settingUp()' in the console if you run the application in the console, and if the slot will get executed.
If the slot will not get executed, the message will not be printed.
This will tell you if the problem is IN the slot, or that the problem is that the slot is not being called.

Just start the program in the console, and see what ouput you get.

No need for 'make all' or any other thing.

[wysota]

He's using Windows, so adding CONFIG+=console and rerunning qmake is advised.

[Salazaar]

I added this, rebuild application, console window opened (and also normal windows application with GUI opened) but the console was clear. What does it mean?

[high_flyer]

it means the slot is not being called.
But at the moment I don't have the time to review you code again...
So check every thing that has to do with the signal/slot connection.

[high_flyer]

post ALL your code.
The one file yo posted looks ok.

[Salazaar]

post ALL your code.

Sure. Unfortunately my files are too big to attach them, I'll post it in rar file
http://download.yousendit.com/049347421EAD445D

[high_flyer]

you should really read and try SIMPLE examples untill you get how the ui aproach works in Qt.

int main(int argc, char *argv[])
  {
     QApplication app(argc, argv);
     QApplication::setStyle ( new QPlastiqueStyle() );
     QDialog *window = new QDialog;
     //Ui::Dialog ui;
     //ui.setupUi(window);
    app.setMainWindow(window);
     window->show();
     return app.exec();
 }

int main(int argc, char *argv[])
  {
     QApplication app(argc, argv);
     QApplication::setStyle ( new QPlastiqueStyle() );
     QDialog *window = new QDialog;
     //Ui::Dialog ui;
     //ui.setupUi(window);
    app.setMainWindow(window);
     window->show();
     return app.exec();
 }

To copy to clipboard, switch view to plain text mode 

[high_flyer]

Do you know how to use signals and slots?

Your kidding me? Of course, I know.

I am starting to think you are kidding me...

class Dialog : public QDialog/*, public Ui::Dialog*/ //what was that for??
 {
     Q_OBJECT
 
 public:
     Dialog(QWidget *parent = 0);
 
 
public slots:  //<<----this is needed      
      bool settingUp();
      void previousStep();    
 
 private:
 
     Ui::Dialog ui;
 };

class Dialog : public QDialog/*, public Ui::Dialog*/ //what was that for??
 {
     Q_OBJECT

 public:
     Dialog(QWidget *parent = 0);
  

public slots:  //<<----this is needed      
      bool settingUp();
      void previousStep();    

 private:
    
     Ui::Dialog ui;
 };

To copy to clipboard, switch view to plain text mode 

[Salazaar]

I think public Ui:ialog is needed to access gui elements

[high_flyer]

as I said, READ about it more.
You have a private ui elements which you use in your Dialog class.
If you use that approach you don't need to sublcass, one of the nice things about Qt4 ui way.