General and Desktop

[quote author="gayu" date="1353498871"]Hope so the link will be helpful for you http://doc.qt.digia.com/qtcreator-snapshot/creator-debugger-engines.html[/quote] I've done what I'd read here, but this not solved my problem...

Ok, I have not tried this myself, but I would try this: Create an object that you install as an event filter on your QApplication. Listen for ShowEvents, and see if the object it was aimed at is a QMessageBox subclass. If so, you can read the text from it and log that.

You're right, I saw that ))), but as I understood DimanNe did find good solution. I've come across the same problem and QWidget::adjustSize() works well and looks better as for me. I posted that just for the case if someone like me has the same problem and check QWidget::adjustSize().

Nice, I'm glad it worked :)

I did it. Thank you so much :)

Anyone about the question of alexandros?

In my example, i mixed old rendering opengl stuff with qquick item which used VBO i presume. I think, it's not a good idea to mixed that. So now i used VBO for my rendering and it's work.

I fix it.. but I not understand how a Simple Dialog with some message text can make this errors appears. Well, I remove the menssage errors and just add to log... it's better for user. Thanks all.

@INeedMySpace There's no argument that subclassing QThread can work -- and indeed it was the only way to use QThread in earlier versions of Qt -- but since that method is rife with potential problems, that particular methodology is deprecated for most common applications and should be avoided if possible.

Thanks rcari and MulderR. The LoadLibrary / GetProcAddress approach works well. Using QLibrary the working code looks like [code] // get process handle DWORD pidwin; GetWindowThreadProcessId(foregroundWindow, &pidwin); HANDLE hProcess = OpenProcess(PROCESS_QUERY_INFORMATION | PROCESS_VM_READ, FALSE, pidwin); // get process path WCHAR szProcessPath[MAX_PATH]; DWORD bufSize = MAX_PATH; QueryFullProcessImageName pQueryFullProcessImageName = NULL; pQueryFullProcessImageName = (QueryFullProcessImageName) QLibrary::resolve("kernel32", "QueryFullProcessImageNameW"); QString processPath; if(pQueryFullProcessImageName != NULL) { pQueryFullProcessImageName(hProcess, 0, (LPWSTR) &szProcessPath, &bufSize); processPath = QString::fromUtf16((ushort*)szProcessPath, bufSize); } [/code] More information on which function to use for the different windows versions - http://msdn.microsoft.com/en-us/library/windows/desktop/ms684919(v=vs.85).aspx

You might want to check out the type of events that Qt can handle. For the given widget you might want to use this one: @QEvent::FocusOut 9 Widget loses keyboard focus (QFocusEvent).@ Then in that event set the value to the one with the icon only to display. Tada, should work Greetz

Creator is probably set to debug, so it will be there. The command will run a executable, so can be anywhere. As Mulder says.....make sure that Qt can find the plugins

Thanks for letting us know. could you please edit your first post and prepend [Solved] to the title? That's how we inform others the topic is solved.

OK, resolved! I set codec on QTextStream and now is working as expected! Thanks

So when using Q3ToolBar and Q3PopupMenu, their actions must be Q3Actions. Otherwise the QAction itself is used right.

[quote author="yupifourbi" date="1353399194"] Is it ok to say just 'return 0;'? As I don't pass anything else after the App/ program ends.[/quote] Interesting approach. It's probably alright, if the dialog works OK, then it should be fine.

Thank you all.I have a try and indeed only the Unix convention works.