General and Desktop

"QNetworkAccessManager::head() ":http://doc.qt.nokia.com/4.7/qnetworkaccessmanager.html#head is your friend. Use it just like a get request.

Thanks, Gerolf. I notice my mistake now.

[quote author="mlong" date="1314403576"]I'm not sure what the behavior of a QDockWidget is if it's not used in conjunction with a QMainWindow. According to the docs, a QDockWidget is designed to be docked in a QMainWindow, not just an arbitrary widget. You can always create a QMainWidget, and set your AdvancedTextEditor as its central widget. Then the dock widget should behave properly. [/quote] Thanks for all the help, =). Solved !! =)..

In future if someone else is in need: "Your text to link here...":http://lists.qt.nokia.com/pipermail/qt-interest/2011-July/034969.html

Thanks a lot. I tried the second one, it perfectly works. Cheers

yes i added QT+=phonon. Can u clarify what is execution directory. phonon4.dll is there in C:/Qt/2010.05/bin directory. Iam saving my projects in C:/Qt/MyProjects directory.

Or have a look at this "recent thread":http://developer.qt.nokia.com/forums/viewthread/9090

[quote author="Lukas Geyer" date="1314266752"]No, but see "here":http://developer.qt.nokia.com/forums/viewthread/9050/.[/quote] That links to this thread - a mistake?

I have posted the root cause, a small project to reproduce it and a temporary workaround in the Bugtracker for this bug: QTBUG-19886 It is caused by a stack mis-alignment of the newly created thread. It affects the drawing engine which expects 16-byte alignment for the used SSE2 instructions. It appears to only occur on windows XP. And happens when a QPainter::drawImage is done on a different thread. The stack on the new thread (QThread subclass and started with start()) is NOT 16-bit aligned, and causes a Segmentation Fault on the MMX instruction PANDN in qdrawhelper_sse2.cpp. The only (dirty) workaround I can think of is to manually push extra bytes on the stack in case it is not aligned to realign the SP to a 16-byte boundary. And this seems to work quite well, no more crashes!

[quote author="kartlee" date="1314379149"] Should we not take it for granted that it works with non Qt threads? [/quote] As the warning is still in the source code, I would say no, it only works with QThread, but not with with threads started using platform-specific APIs or other libraries like boost.

Thank you for your answer. It's very helpful for me.

AFAIK it was not merged. But it's pretty easy to use and works like a charm... :-)

They keyword in the warning is, I think, sibling widgets. That is: widgets that are at the same level of the GLWidget, instead of being child widgets of the GLWidget.

-Please mark the topic as [Solved] by editing the title of the topic from your first post.- Edit: You already did. Thanks :-)

I think you are battling the window manager here, not Qt. For me, it makes sense that no dialog boxes of other applications are allowed over an application that runs full-screen, but your or the window managers opinion may differ on that. That it works if you set your own application to run full screen as well makes perfect sense then too. Thanks for reporting back though.

You're welcome :P

Well, loading the file and encoding it into base 64 then passing it as a data: object to setUserStyleSheetUrl works around the problem with actually locating the file, but the table rendering is still broken. I've tested this with third party CSS as well as my own and confirmed that the table is rendered correctly if I embed the CSS in the HTML with a style declaration. Can anyone explain why the rendering would be different using setUserStyleSheetUrl than when embedding the CSS with a style directive in the HTML? Thanks.

I have alreday shared the solution Eddy.., :-)

and it should be like this @bool gwMainWindow::winEvent ( MSG * msg, long * result ) { if (msg->message == WM_NCLBUTTONDOWN) { int nHittest = (INT) msg->wParam; if (nHittest == HTCAPTION) { //here catch the lbuttondown event only on titlebar } } }@

Tell us even more. Make a drawing of what you want to achieve for example. We want to understand your use case, so we can help you. One line isn't enough.