We have also gone down the forced ANGLE route after seeing too many crashes
caused by OpenGL, crashes on app start during the dynamic detection are
particularly frustrating. Intel cards seem to be the worst offender though
we were seeing them from all card types.
When our app crashes we upload cra
Not sure on your platform but we had some problems running a websocket
server on Mac non-openssl build due to the QNetwork's Secure Transport
based implementation not supporting pkcs8 keys, the full certificate chain
(ca-bundle) was required to be present too, which wasn't on Windows using
openssl
We recently enabled switched our app over from forced ANGLE (via
AA_useOpenGLES) to the dynamic detection, however this has resulted in a
large increase in crash reports from users so we would like to go back to
using ANGLE but we would like to allow software rendering too based on the
included ope
deleted or not, and I don't see how
> that's tedious. However, when you are mixing a slot connected to
> destroyed and QPointers, you start depending on the order of slots
> called. To avoid this, I'd use a queued signal or handle it in some
> other way. For this, we n
Below is a example program which will crash when the widget is closed.
This setup replicates the QWebview behaviour where it will emit the
loadFinished signal from inside the destructor if a page is loading.
I am wondering if anyone can suggest a clean way of handling this sort of
case, where a s
You can use QQmlEngine::setNetworkAccessManagerFactory to make the Image
element use your own QNetworkAccessManager instances, which in turn you can
set a cookie store on that contains your session cookie.
http://doc.qt.io/qt-5/qqmlengine.html#setNetworkAccessManagerFactory
Note that setNetworkAc