Hi,

You may have found a bug. You should check the bug reports system to see if it's something known. If not, please consider opening a new report providing a minimal compilable example that shows that behavior.

Hi, just to want add, while Qt Creator's capturing of your qDebug() output is usually 100%, but if you want to be sure to get everything, you could try running DebugView when your app exits.

@Simurr
Hi,

I am not sure whether WiFi Direct is among the supported APIs which can be co-used for classic apps. But usually you need to take care of a couple of things.

Most promintently you will need to link against runtimeobject.lib to find Activation symbols.
I just pushed a change for positioning to showcase, how a "generic" porting from WinRT to classic apps can work. See https://codereview.qt-project.org/#/c/159330/ for some details.

This seems to be a problem with a Qt Desktop app trying to use the WinRT libraries using C++/CX. I am getting the same error for every WinRT API call (WiFi Direct stuff) I've tried so far.

Can Qt 5.6 use C++/CX to use parts of the WinRT API? Either this isn't going to work or I'm missing something that I would think would be documented somewhere.

@jsulm said:

@Pixtar You can use Visual Studio 2013 Community which is more or less same as Professional.

Thanks for the hint. :D

I found the same problem with Marcosabba on Qt 5.5 for Winrt, too.
I have just tried to rebuild my application on Qt 5.6, today, it is fixed.
Drop down is shown below combobox control. But it still has a strange behaviour.
When item is dropping down, there is flicker frame.
FYI.

@SGaist Thank you! I will bring this question to the interest mailing list.

Hi and welcome to devnet,

That's a question better asked on the interest mailing list. You'll find there Qt's developers/maintainers (this forum is more user oriented)

Hi,

for 32bit you will need to compile Qt on your own. We provide the most common derivates (64bit and ARM) only as otherwise the packages would simply become to big.

For reference you can find the documentation here:
http://doc.qt.io/qt-5/winrt-support.html#building-from-source

The mkspec of choice would be winrt-x86-msvc2013 then.

Thanks.
I couldn't find a bug myself but it seems there is one, so in the event that someone else might be interested it is https://bugreports.qt.io/browse/QTBUG-43837.

QtMultimedia's backends uses the platform API so AVFoundation on OS X, WMF/DirectX on windows etc. The GStreamer backend is used on non-android non-mac unix variants.