Thanks Andrew & Thiago. I've tested the app with Qt 5.5.1 but I can test it with 5.6 for sure. On the bright side I should say that the rest of the app works quite well. We heavily rely on QTcpSocket and that works perfectly fine, as far as I can tell. Same goes for the QML stuff, like Canvas. In short the overall feeling is more than positive! :)
@Andrew, I've another question. You wrote in QTBUG-45495 <https://bugreports.qt.io/browse/QTBUG-45495> that: "The platform transparently uses the system proxy, but let's accept this task as an investigation into whether it is possible to hook up any of that information/control into the Qt API." Ok, so we can basically take out the usage of QNetworkProxy from libraries using it, e.g. KDSoap, right? We have currently recompiled the library using #ifdef for the offending part. Thanks again, F. On 19 October 2015 at 21:39, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Monday 19 October 2015 19:55:44 Federico Buti wrote: > > but it seems that the feature in not supported in Qt since CanBroadcast > > flag is set to false in QNetworkInterface (or am I misinterpreting?) > > That might be a false negative beucase QNetworkInterface for WinRT never > sets > CanBroadcast, for any interface. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
