View Single Post
Old 02-08-2020, 12:57 PM   #25
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,708
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
QSurfaceFormat is bit of a giveaway for me, here.

@KevinH, do you think that the info provided here: https://doc.qt.io/qt-5/qtwebengine-platform-notes.html

Quote:
Default QSurfaceFormat OpenGL Profile Support

If a new default QSurfaceFormat with a modified OpenGL profile has to be set, it should be set before the application instance is declared, to make sure that all created OpenGL contexts use the same OpenGL profile.

On macOS, if the default QSurfaceFormat is set after the application instance, the application will exit with qFatal(), and print a message that the default QSurfaceFormat should be set before the application instance.
coupled with Kovid's enabling of Qt.AA_ShareOpenGLContexts in calibre's source (https://github.com/kovidgoyal/calibr...init__.py#L885) is relevent to this message?

Maybe we should enable Qt.AA_ShareOpenGLContexts early on as well??
DiapDealer is online now   Reply With Quote