Re: [Interest] QWebEngineView + QSurfaceFormat == errors in console

Thanks Sean. One of the problems is likely that I'm using Qt3DWindow which calls QSurfaceFormat::setDefaultFormat() in the constructor which I've already called in main(). I'd missed this warning in my application's output because I have a bunch of debug output: Warning: Warning: Setting a new de

Re: [Interest] QPixmap and threads

05.05.2017, 11:26, "Giuseppe D'Angelo" : > Il 05/05/2017 09:05, maitai ha scritto: >>  But still, I have hundreds of other QPixmaps used in threads, with no >>  problem at all (creating, painting, etc). All is working fine for years, >>  without any warning or so from Qt. > > Well, not having pro

Re: [Interest] QPixmap and threads

Em sexta-feira, 5 de maio de 2017, às 00:05:09 PDT, maitai escreveu: > But still, I have hundreds of other QPixmaps used in threads, with no > problem at all (creating, painting, etc). All is working fine for years, > without any warning or so from Qt. Should I change also all these > QPixmaps to Q

Re: [Interest] Licensing PITA

On 5/5/2017 12:03 AM, Rainer Wiesenfarth wrote: 2017-05-04 20:02 GMT+02:00 Bob Hood >: I am trying to create a commercial, static build of 5.7.1 ​I ran into a similar problem with building a commercial Qt 5.6.x ​from the Git repo. This does not work out-of-the-b

Re: [Interest] Licensing PITA

On 5/5/2017 4:11 AM, André Somers wrote: This sounds like exactly the kind of issue you'd contact your commercial support for? You're probably right, André. Licensed users who build Qt for themselves appear to hold "mythical creature" status. :) ___

Re: [Interest] Licensing PITA

Op 04/05/2017 om 20:02 schreef Bob Hood: > I have a legitimate Qt license (just renewed, in fact). I am trying > to create a commercial, static build of 5.7.1, and the build output > keeps coming up with: > > Licensee > License ID.. > Product license..

Re: [Interest] QPixmap and threads

Ok, thanks all for your comments. I'll change them all then. BTW what is the "right format for display? Format_ARGB32_Premultiplied maybe? Philippe. Le 05-05-2017 10:25, Giuseppe D'Angelo a écrit : Il 05/05/2017 09:05, maitai ha scritto: But still, I have hundreds of other QPixmaps used in

Re: [Interest] QPixmap and threads

Il 05/05/2017 09:05, maitai ha scritto: But still, I have hundreds of other QPixmaps used in threads, with no problem at all (creating, painting, etc). All is working fine for years, without any warning or so from Qt. Well, not having problems doesn't imply that what you were doing was correct

Re: [Interest] QPixmap and threads

> If QPixmaps are forbidden outside the main GUI thread, why is it not written in the documentation? http://doc.qt.io/qt-5/thread-basics.html " All widgets and several related classes, for example QPixmap , don't work in secondary threads." Best Jean-Michaël

Re: [Interest] QPixmap and threads

On Fri, May 5, 2017 at 10:05 AM, maitai wrote: > Should I change also all these QPixmaps > to QImages (with a conversion cost at the end of the threads)? Probably. > If QPixmaps are forbidden outside the main GUI thread, why is it not written > in the documentation? It isnt't? I recall there's

Re: [Interest] QWebEngineView + QSurfaceFormat == errors in console

On Thursday 04 May 2017 17:57:32 Thiago Macieira wrote: > Em quinta-feira, 4 de maio de 2017, às 16:07:12 PDT, Andy escreveu: > > Fatal: QWebEngine: Default QSurfaceFormat OpenGL profile is not compatible > > with the global shared context OpenGL profile. Please make sure you set a > > compatible Q

[Interest] QPixmap and threads

Hello, I have read in many places that QPixmaps should not be used in threads (Qt5.8/QtConcurrent in my case). In fact I have discovered that fact only recently, because I had a random crash occurring on QPixmap::load(), and in the end that was occurring when QPixmap::load() was used exactly