Message QWindowsNativeInterface::nativeResourceForWindow: 'handle' requested for null window or window without handle.
-
[quote author="xisuosunboy" date="1360592779"]只要创建widget,就是一大堆QWindowsNativeInterface::nativeResourceForWindow: 'handle' requested for null window or window without handle.
QT Example has the same problem in QT5.0.1!
QT5.0.1 win7 32bit mingw4.7/vs2010 (official build)[/quote]Can you please point me which example and what steps required to see this , i just ran few widget based example and dont see this.
-
[quote author="irfan.omair" date="1360629199"]
[quote author="xisuosunboy" date="1360592779"]只要创建widget,就是一大堆QWindowsNativeInterface::nativeResourceForWindow: 'handle' requested for null window or window without handle.QT Example has the same problem in QT5.0.1!
QT5.0.1 win7 32bit mingw4.7/vs2010 (official build)[/quote]Can you please point me which example and what steps required to see this , i just ran few widget based example and dont see this.
[/quote]
"Application Example",When you click to "open" or "save",then there will a lot of "QWindowsNativeInterface::nativeResourceForWindow: 'handle' requested for null window or window without handle."
Whether in "debug" or "release",this problem occurs.
-
When in windows2003 .QT5.0.1 32bit mingw4.7 (official build)
“Application Example”,When you click to “open” or “save”,then there one message like this "CoCreateInstance failed (在活动的激活上下文中没有找到任何查找密钥。)"
-
Alright, so it seems it is coming up when you are actually trying to show native dialog. Let me try to reproduce it here
-
[quote author="irfan.omair" date="1360695750"]Alright, so it seems it is coming up when you are actually trying to show native dialog. Let me try to reproduce it here[/quote]
Did you able to reproduce this problem?Or the problem is only my case.
-
I'm sure it is not only your problem. As you can read in thes thread, many others are affected as well.
-
Yes I was able to reproduce it and have fix if you guys are willing to apply the patch.
-
fix is already in the repo so feel free to use latest or find the patch from there, commit is ac864956f8ba6f6cb527725a4347babab2a1e498
-
[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]
Received, thank you very much. Although I do not know how to fix the patch, had to wait for 5.02.
I will continue to learn.
Thanks again. -
[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 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