General and Desktop

Thanks I'ill try this way.

No. By feature I mean qmake "configuration features":http://doc.qt.nokia.com/stable/qmake-advanced-usage.html#adding-new-configuration-features found in $QTDIR/mkspecs/features. I took a quick look at it and it looks like that the test feature is called testlib, not test. So it is either QT += testlib or CONFIG += test. However, do yourself a favor and do not use module wide includes like #include <QtTest>. It is a bad habit and it will strike back at you and you will end up in fixing it somewhen.

This is a feature unique to QButtonGroup. See Vass' post for a solution. Depending on how you manage the lifetime of your objects you might use QHash<int, QImage*> instead.

Great! Could you edit your title and add [solved] in front of it? Thanks.

solved. i needed the following code. @ tc.movePosition(QTextCursor::End); plainTextEdit->setTextCursor(tc);@

you can use applicationviewer from qt qml.

ok i will try.............

I think there is lucking code or may be there is something wrong with the system.

For blink rate, you can try @ qApp->setCursorFlashTime(0); @

Volker: Thank you for this info, I will certainly try to remember this from now on........ Thank you all for all of your responses.

No, not that I know off. But you could make your delegate just expose the default behaviour for all cells that do not match certain criteria.

KDE's Solid API (which is implemented on Linux, Windows and Mac) has the concept of a Device UID. That is basically what you seem to be looking for, and it is appearantly feasable to implement that on all the platforms. Note that if you want to list the storage media on the system, you can also use Qt Mobility SystemInfo API' s (also works on the desktop!) to list the devices, and get access to the URL's they reside on.

The big question is: why do you do this? Why make your socket handling first asynchronic by putting it in a thread, and then use synchronic programming again within the thread? Why not use the asynchronic programming methods directly and get rid of both the thread and the waitFor* methods?

Now it works, thank you!

In genereal, it works with beginResetModel / endResetModel if you change the whole model. If you update a value, use dataChanged signal. If you only insert a row or a column, use beginInsertRows() and endInsertRows, resp. Columns.

Just keep pointers to your Actions in MainWindow class and change Actions state on QTabWidget::currentChanged ( int index ) signal