Message QWindowsNativeInterface::nativeResourceForWindow: 'handle' requested for null window or window without handle.
-
[quote author="irfan.omair" date="1360970748"]fix is already in the repo so feel free to use latest or find the patch from there, commit is ac864956f8ba6f6cb527725a4347babab2a1e498 [/quote]
I got the same problem, thank you omair for providing a fix.
-
Also on QT5.0.2 - Qt Commercial MinGW on Win7 64
-
Also on Qt5.0.2 commercial, compiled with VS 2012.2 v110_xp 32 bit:
Warning:painting\qbackingstore.cpp (101:void __thiscall QBackingStore::flush(const class QRegion &,class QWindow *,const class QPoint &)) - QBackingStore::flush() called with non-exposed window, behavior is undefined
-
Solved my reporting of "QWindowsNativeInterface::nativeResourceForWindow: ‘handle’ requested for null window or window without handle."
This was was due to one of my DLLs being built by an earlier version of Qt.
Once I rebuilt all of the code used in my project the error messages stopped.
-
thanks, my warnings are slightly different - it complains about non exposed windows...
-
Hi
I want to know step by step how I can fix this problem.
Thanks. -
What kind of warning do you have in detail?
"QBackingStore::flush() called with non-exposed window, behavior is undefined"
or
"QWindowsNativeInterface::nativeResourceForWindow: ‘handle’ requested for null window or window without handle."
the latter one was fixed in 5.0.2 as far as I know, the first one still exists. In my app, the first warnign raises as soon as I tabify a dockwidget which is currently hidden.
I have reported this issue to comemrcial support but did not get any response yet :/
regards,
Torben -
the second one
“QWindowsNativeInterface::nativeResourceForWindow: ‘handle’ requested for null window or window without handle” -
Have you upgraded to 5.0.2?
-
I got this error on 5.0.1 but I have the 5.0.2 setup
-
well, then test it if the warning still occurs on in the current stable release (5.0.2) -ideally before asking for support ;)
Good luck!
-
Ok! I didn't know that the 5.0.1 is unstable. Thanks!
-
hi,
5.0.1 is not unstable, but it is not the current stable release.
If you have a bug, it's always worth to verify that the used Qt version is the current stable release. If not, maybe the error is already fixed in the current stable release ;)
-
I get a lot of those messages with that call:
QFileDialog::getOpenFileNames()
-
Cyttorak: sorry, I lost my crystal ball yesterday, so I cannot help you...
...If you really want to get help, you should provide at least a minimal set of information:
which OS and with Qt version you use.Torben
-
Excuse me TorbenD for that poor example. I will create a minimum project in order to provide a better showing of this issue. Is there any jira about this problem so I can upload the example project?
Thank you
-
Cyttorak,
no need for a project, just tell us what OS and what Qt version you use!!
I assume 5.0.1 since I got the warnings you describe in 5.0.1.
so:
a) what is your operating system you use?
b) what is your Qt version you use? -
Ok! :)
a) Windows 7 64 bits
b) Qt version 5.0.1, Mingw 4.7 32 bitsAnd as I said before I get those messages opening a QFileDialog window with getOpenFileNames() method.
-
good boy :D
hm as I assumed... Why haven't you upgraded to the current stable release 5.0.2 and checked whether the problem still exists or whether it is fixed already?
Then you would have discovered that the error you describe was fixed in 5.0.2 already.
please follow these instructions carfully to make your life easier:
If you have a problem/bug, please verify at first that you use the latest Qt release. Releases increasing the third number are called "bugfix release" (e.g. 5.0.1 -> 5.0.2), because they FIX BUGS.
--> If you have a bug and need a bugfix - ensure you have the current bugfix release of Qt installed (is your Qt version identical to the Qt version provided at http://qt-project.org/downloads).
It's unneccessary to ask for new bugfixes without testing whether currently available bugfixes in the current stable release solved the issue already. :)
It is no personal offence, but I try to educate people for a structured apporach solving their own problem solution instead of shouting for support. This means a) upgrade to the newest version, verify if the problem still exists before you ask b) provide a minimal set of information to allow others to help :)
Enjoy :)
-
Thank you for your time, TorbenD. I will update to bugfix release some time in the future :)