General and Desktop

@ QDomDocument doc("QDNTest"); QDomProcessingInstruction xmlVers = doc.createProcessingInstruction("xml", "version="1.0" "); doc.appendChild(xmlVers); QDomElement root = doc.createElement("QDNTest"); doc.appendChild(root); qDebug() << doc.toString(); @ This creates output @ <?xml version="1.0" ?> <!DOCTYPE QDNTest> <QDNTest/> @ To strip the DOCTYPE from the XML, construct the document without argument: @ QDomDocument doc; QDomProcessingInstruction xmlVers = doc.createProcessingInstruction("xml", "version="1.0" "); doc.appendChild(xmlVers); QDomElement root = doc.createElement("QDNTest"); doc.appendChild(root); qDebug() << doc.toString(); @ This creates output @ <?xml version="1.0" ?> <QDNTest/> @

Not solved as such, but just to wrap up this thread, I've found an alternative way of doing what I want. If I dispense with the QGraphicsView and just use a QSvgWidget, storing the image in a QByteArray, I can manipulate the SVG elements in memory and just reload the data into the widget. It's actually a simpler way of achieving the samer result, though the speed of rendering seems even slower.

I am not sure if you really want to go through a qbytearray. You can manipulate the images directly as it was suggested in "your other post":http://developer.qt.nokia.com/forums/viewthread/14323/

[quote author="aurora" date="1329208881"] code in adding tab @ ui->tabWidget_unfiltered->addTab(filesTable,FileName); @ and for closing tab @ QWidget *tab=ui->tabWidget_unfiltered->widget(index); ui->tabWidget_unfiltered->removeTab(index); delete tab; // <-- @ [/quote] The widget is deleted correctly. Again, a non-shrinking working set does not prove a memory leak by any means. Your system library may or may not return the memory on delete, the operating system may or may not leave unused pages in the working set. If you think you might have a memory leak use a dedicated tool, like valgrind, Purify or Visual Studio to detect the leak, not the Windows task manager (or any other similar tool, like top). The source of your "memory leak" is the use of an improper tool to detect it.

ok thank u...

you can try to set the "sizePolicy":/doc/qt-4.8/qwidget.html#sizePolicy-prop and/or the horizontal/vertical stretch on the widget. The "layout management":/doc/qt-4.8/layout.html docs have the details.

Yes, my program wil be one of the sub system of huge software product, which developing was started long time earlier when Qt 3 was the latest version. And now it is impossible to re-develop this project to newer version of Qt.

Unfortunately, we are running on Windows...I guess I could just tell users to change their time zone to somewhere without DST ;) I wonder how that would fly!

I don't think you need implement a Template Class and inherit all of its classes. Just override the changeEvent(QEvent* event) function on widgets from your View Layer, like that: @void MyWidget::changeEvent(QEvent* event){ if (event->type() == QEvent::LanguageChange) { widget.retranslateUi(this); } QWidget::changeEvent(event); }@ I hope that helped.

Be sure and tag your post as [Solved]. Thanks!

[quote author="aurora" date="1329131080"]I am reading line by line and displaying them in QTableWidget but as the file size increases, program crashes or hangs….what should i do, in this case? How can i load such big files in QTableWidget?[/quote] No way. Possibly you could try QTableView but your mileage may vary [quote author="aurora" date="1329131080"]How can i perform searching efficiently on them?[/quote] You should build something like a binary search tree on the data [quote author="aurora" date="1329131080"]Does Qt provides any good mechanism for these kind of problems? [/quote] The cruel answer is no, qt won't help you in any of these problems. You should rely only on your sheer C/C++ skills in such questions if you want to create something workable. In short, you will have to write your own file engine or use an existing one to work directly off disk (relational DBMS won't help you either). And probably you will have to exclude qt from everything that deals with large datasets. For sure somebody will get up here and point a finger at me but before blowing fire read "this":http://bugreports.qt-project.org/browse/QTBUG-18490

One thing I can add here: You need to: setAttribute(Qt::WA_TranslucentBackground); on both the Viewport (QGLWidget) AND the QGraphicsView On my linux machine with a compositing manger running I can have opengl-painted qml applications with "holes" :) Now I add a questions: This is not working on windows (with running aero) ... anyone an idea why?

You are welcome, I hope I didn't misinform you by accident, I myself am fairly new to programming.

Sorry, I misunderstood your posting at first. Manually calling QTooltip::hideText() does what I need. Thanks!

The Windows UI styleguide, to name just one, disagrees. The Enter key is "supposed":http://msdn.microsoft.com/en-us/library/ms971323.aspx#atg_keyboardshortcuts_fundamentals_of_keyboard_ui_design to trigger the default action of a dialog. I'm sure similar rules apply to OS-X, KDE and Gnome. You may think it is a bad idea, but I think it is a bad idea to break UI standards. And the standard is to trigger to default action.

[quote author="yashaswiram" date="1329306420"]plz can i get codes in pyqt4 ....[/quote] No. I'm not going to re-implement the code I pointed you to in Python just to make you happy.

Did you take a look at the Finger Paint example? You only replace QTouchEvent with QMouseEvent. Regards, Jake