Hi,
I reported this bug a while ago, yet it seems unhandled:
https://bugreports.qt-project.org/browse/QTBUG-35821, which along with a couple
of other bugs makes it embarrassing to ship an application for Mac @ Qt5.x.
In my opinion it’s a showstopper. How do “normal” people like me make sure th
Would someone familiar with widgets please kindly review this patch or
suggest an alternative fix. I'm happy to update the patch if a better
solution exists. This regression is preventing my company from moving from
Qt4 to Qt5.
https://codereview.qt-project.org/#change,72939
__
Given that there exists a web idl for Web sockets, I suggest the qml api to
consist of a QML element and a Javascript constructor. The prototype and the
qml element should probably have the same api, the web Standard one.
It is in our interest that third-part JS code out there using web sockets
2014/1/18 Kurt Pattyn
>
>
>
>
> On 18 Jan 2014, at 01:18, Konstantin Ritt wrote:
>
> After a brief review, I have a strong feeling that QWebSocket doesn't fit
> QtNetwork at all.
>
> The main reason I see is that that QWebSocket isn't really a Q*Socket in
> QtNetwork sense, it is actually a pro
