My first program in QT
-
From what you said, I guess you know the answer, but for your own reasons don't wish to reveal it. I see by observing parts of code in more complicated examples that my syntax is correct. Unfortunately, QT is not standard C++. If it was there wouldn't be this foolishness of Slots and Signals instead they would use Methods and Events as in standard C++. . I'm either going to have to get some answers either by waiting and hoping someone else will pitch in and help me or by creating another thread. I asked a simple question. Why can't I get a simple, complete answer. Is knowledge of QT hoarded and only given out bit by bit? I have a book by the way. It's just not a book on QT
Thanks,
Paul -
[quote author="p3aul" date="1337383959"]From what you said, I guess you know the answer, but for your own reasons don't wish to reveal it. I see by observing parts of code in more complicated examples that my syntax is correct.
Paul[/quote]
Sorry.And Sorry for my poor English.
As C++ builder is a IDE of C++, and you said that you used to C++ builder, so I wrongly thought that you will be very familiar with C++, but seems you not.
Qt is a library of C++, it isn't a good idea to deep into the Qt world before familiar with C++. Perhaps “C++ Primer” is a good book to start with.
bq. Unfortunately, QT is not standard C++. If it was there wouldn’t be this foolishness of Slots and Signals instead they would use Methods and Events as in standard C++.
It depends.
All the “non-standard” sources will be pre-processed by moc, uic, rcc, and then all you get are C++ “standard” files.
No matter what happened, your Qt application will be compiled by a “standard” C++ compiler such as GCC, MSVC, Intel-C++, Clang, ..., even C++ builder.
-
Main Window .cpp
@#include "mainwindow.h"
#include "ui_mainwindow.h"MainWindow::MainWindow(QWidget *parent) :
QMainWindow(parent),
ui(new Ui::MainWindow)
{
ui->setupUi(this);
}MainWindow::~MainWindow()
{
delete ui;
}void MainWindow::on_pushButton_clicked()
{
lineEdit->setText("Hello");
}
@Errors:
/home/owner/qt/newattempt-build-desktop-Desktop_Qt_4_8_1_for_GCC__Qt_SDK__Release/../newattempt/mainwindow.cpp:-1: In member function 'void MainWindow::on_pushButton_clicked()':
/home/owner/qt/newattempt-build-desktop-Desktop_Qt_4_8_1_for_GCC__Qt_SDK__Release/../newattempt/mainwindow.cpp:18: error: 'lineEdit' was not declared in this scopeThis error about lineEdit seems to indicate that I need to declare it somewhere in mainwindow.cpp I don't know if this just the tip of the iceberg though. Once that is corrected others may show up. :(
-
[quote author="Wilk" date="1337390529"]Well, the simpliest solution is to declare a signal like sendText (QString) and connecting it with slot of your QLineEdit like setText, and then emit it in your on_pushButton_clicked () slot.[/quote]
It's an answer, but not the simpliest ;-) .The right answer have been given by VanDerSam. And I try to given reasons, but failed ;-(
-
[quote author="p3aul" date="1337390576"]Robot Herder: I have an excellent book that came with C++ builder version 3. The syntax is correct. In Builder I didn't need to add declarations of Components(Widgets) because Builder added them automatically.[/quote]
If I am right, you never try to see the code behind the drag and drop operation when using C++ builder.
-
Wilk:
@Well, the simpliest solution is to declare a signal like sendText (QString) and connecting it with slot of your QLineEdit like setText, and then emit it in your on_pushButton_clicked () slot.@
That's a perfect example of what I'm talking about. What you wrote is NOT C++ it's Qt! I need a book on Qt, not C++!If that's the simplest solution than I need to go back to windows and CodeGear or Visual C++
-
The fact is that VanDerSam's solution makes your program dependent on UI and actual names of it's components, while you can change UI itself and/or it elements and/or names of UI elements. While my solution makes your application dependent only on interface of class.
-
Robot Hearder:
@If I am right, you never try to see the code behind the drag and drop operation when using C++ builder.@Well yes, except for the code snippets you write your self. Let's face it, I'm no purist! I just want to get the job done, and Qt, like C++ builder is a RAD tool. Otherwise you would all just use a text editor and code it all for the fun of it.
-
[quote author="p3aul" date="1337391158"]Wilk:
@Well, the simpliest solution is to declare a signal like sendText (QString) and connecting it with slot of your QLineEdit like setText, and then emit it in your on_pushButton_clicked () slot.@
That's a perfect example of what I'm talking about. What you wrote is NOT C++ it's Qt! I need a book on Qt, not C++!If that's the simplest solution than I need to go back to windows and CodeGear or Visual C++ [/quote]
You're free do do what you want, but Qt is better at least because it's cross platform. If you don't want to learn something new it totally your problem.
P.S. Use "quote" function instead of code blocks highlighting for quotes. -
;-) Seems you don't know which problem encountered and complained by p3aul.
What he need is a C++ book, no matter which GUI library he want to use.
- Qt
- MFC
- wxWidgets
- ...
And which C++ IDE he want to selected
- Visual Studio
- C++ builder
- Ellipse
- Qt Creator
- ...
And which C++ compiler he want to choose
- cl.exe (MSVC)
- g++.exe
- clang.exe
- ....
[quote author="Wilk" date="1337391395"]The fact is that VanDerSam's solution makes your program dependent on UI and actual names of it's components, while you can change UI itself and/or it elements and/or names of UI elements. While my solution makes your application dependent only on interface of class.[/quote]
-
I'm using the code format rather than the quote format because that's the only that I can figure out hon this forum. I guess I need a book on Qt forums also? Every one insists that i don't know C++ while I have proven that my syntax is correct. It's just a dead horse you're trying to beat. I know enough to know that I'll will never get an answer here because you are all die-hard loyalists to Qt who can't even accept its deficiencies. Well i guess this post will get me thrown off the forum, but it's just as well. Qt being what it is, i guess ya'll just love java!
Robot Hearder:
@If I am right, you never try to see the code behind the drag and drop operation when using C++ builder.@Well yes, except for the code snippets you write your self. Let's face it, I'm no purist! I just want to get the job done, and Qt, like C++ builder is a RAD tool. Otherwise you would all just use a text editor and code it all for the fun of it.
@The right answer have been given by VanDerSam. And I try to given reasons, but failed ;-(@
VanDerSam suggested that I use:
ui->lineEdit->setText(“Hello”); and I tried it and came up with about 13 errors. I know I copied and pasted it to replace the code I had written so I know that I used his syntax. Now what is it about that line that makes it the best solution?
Thanks,
Paul -
@1+1=2
If p3aul needs some book about C++ why than he started a thread here?
@p3aul
You've mentioned that events are from standard C++... AFAIK they are not. Furthermore, if you think that signals and slots are foolishness, then you just don't understand the idea of them.
And I didn't tell that you don't know C++. -
Wilk:
Mia culpa! you are right Events are a MS windows thing. C++ in the windows environment just makes use of them. Methods though are C++ (and Pascal/delphi which calls them functions) I guess I can sorta see why Qt would choose Slots and Signals I just wish they had chosen something a little more descriptive and a little less arcane! ;)Well it's not like I'm trying for a career as a professional programmer. I'm 70 years old and nobody would hire me anyway! But I used to Program! I learned on an NCR with 64K of memory. A lot back then!
I guess I'll stick with web programming Since the scripts are easier and I can even use them on my Linux machine, I guess I'll stick with that. -
AFAIK you use signals not to interact with mouse, but to interact with button. Button has it's own method for processing mouse events. When you push button, it processes this event and emits signal.
You have to use signals to get text into textbox because it's a more flexible way. As I've mentioned, you may totally change your UI, for example use text edit area instead of line edit. You may also use UI, created with desigber separate from your app, and then you will still be able to work with it just thanks to signal/slots.
Furthermore, in you example you may also try
@
#include "mainwindow.h"
#include "ui_mainwindow.h"MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent), ui(new Ui::MainWindow) { ui->setupUi(this); } MainWindow::~MainWindow() { delete ui; } void MainWindow::on_pushButton_clicked() { QLineEdit *lineEdit = findChild <QLineEdit *> (); if (lineEdit) { lineEdit->setText("Hello"); } }@
In this code you ask, if main window has line edit element, and if it does, you set it's text. -