General and Desktop

In fact, this is a pure C++ problem. As you can't compile your C++ program into one file and have it run on windows, mac, and Linux. However, if you using pure qml, there is another problem.

You're welcome. Although it took relatively long for the problem to get solved ^^

[quote author="1+1=2" date="1333671273"]What I mean is, write a cross-platform serialport application with GUI is rather easy too. But you have make an easy problem become complexed, as you get a platform special project file, and you want to compile it under another platform. Cross-platform examples can be found from google too. such as http://docs.qextserialport.googlecode.com/hg/1.2/examples-uartassistant.html[/quote] Thanks after I used part of this lib's example for made the project but I had to add a timer and a customizable filter for the output data.

That is actually what I want. But thanks a lot for the clarification. I love this forum! Thanks a lot

thNx Volker for this valuable info.

The Value variable holds the position of the scroll bar. It varies from 0 to 99. The below code is present inside the HScrollbar value change event: QRectF sceneRect = plotScene->itemsBoundingRect(); plotScene->setSceneRect((value * ((sceneRect.width())/100)),0,600 ,350); If the ScrollBar position is 0, then the QGraphicsView should hold the QGraphicsScene data from the left edge of the GraphicsScene to the width of the view area. If the ScrollBar position is 99, then the QGraphicsView should hold the QGraphicsScene data from the right edge of the GraphicsScene to the width of the view area. Same kind of behavior, i am expecting for all scale levels. But it is not happening.

Ok, but how I accomplish that? How can I show the button over the GLWidget?? Has somebody an idea about that?

There is no need to recompile all of Qt to compile the MySQL driver. You can build it separately. That will result in a much faster connection with MySQL than via the ODBC driver. So, I would not recommend your approach.

If you think your needed changes are generic enough, you might also considder creating a patch for Qt itself, and contributing that back so others can use it as well in the future, and you don't have to maintain your own copy of QLineEdit and all that is needed for that for the indefinate future...

Hiding the data from the view does not stop you from using the data in other contexts...

Actually, uic normally produces a .h file, not a .cpp file... Note that qmake will make sure that the uic tool is called on all .ui files that you list in the FORMS section of your .pro file.

All I get from your question, is that you want to write a download manager (who uses these things any more?!), but you have not the faintest idea of what that entails, as you need help on basically every step of the way. Perhaps you should re-think your goals?

Sorry, we're not here to debug your code. You're not even describing your symptoms...

Andre thanks for your help. I have made some changes in program and it worked. @ QApplication a(argc, argv); mainWindow *w=new mainWindow; mainWidget *mw=new mainWidget; w->setCentralWidget(mw); w->show(); QObject::connect(mw, SIGNAL(signalForShowMessageInStatusBar(QString)), w, SLOT(slotForStatusBarMessage(QString))); mw->functionDatabaseOpen(); return a.exec(); @

I think it would be best to raise this issue on IRC. Get onto the freenode network, and pop into the @qt-labs channel. That's where the developers working on Qt itself hang out. There you can discuss if your suggestions are feasible or not. There might be technical reasons for these missing operators, such as the technique used for QStringBuilder not working with these operators... However, a lot of technical insight in how this class actually works interally is needed to answer such questions, and you'll find a lot more of such knowledge on that channel.

I don't think there currently is a fixed plan. It certainly wasn't planned to be released in Qt 5.0. Perhaps in a later . release? I guess it will be on the table again at the Qt Contributors Summit in June.

I think the best way to go forward is to make your checkboxes available as fields in the wizard (read the documentation on those!). Then, subclass QWizard, and reimplement the nextId() function. That way, you can control which page is the next page. As you can access fields from the wizard as well, you can find access the values of the checkboxes from that function, and return the right value accordingly.

You're welcome, have fun learning Qt!