Does Qt 5.5's 3D 2.0 advanced 3d view classes support render thread be seperated from main gui thread?(in a new thread?)
In Q3D 1.0 version, i used QGLView (currently Q3D 1,0 is deprecated and classes are changed), and had come up upon the following technical constraint of not being able to seperate rendering thread from main GUI thread and allocate a new rendering thread to QGLView(maybe it was possible, yet i could not established since QGLView does not inherit from QPaintDevice but all of the scenegraph nodes expect QPainter in their draw callbacks).
Now the module is totally changed, and would like to query the following topic, for QT 5.5's Q3D 2.0 module, for advanced view classes available, is it possible to give the rendering task to other thread (seperate the rendering job from main QT UI thread) because, in some application scenarios, you might want to have 100% performing dynamic 2D ui on one side and include 3D view inside the application for whom's framerate is not expected to bother the main application's general responsiveness or features.
For Qt 5.5's Q3D module, is it possible to have seperate thread or if not possible, would new classes provided to be able to move the rendering thread of advanced 3D 2.0's view classes to seperate thread?
Thanks in advance
Hi and welcome to devnet,
That's a question you should rather bring to the interest mailing list You'll find there Qt's developers/maintainers (this forum use more user oriented)
Thank you very much for the correcting information,
(After successful subscription, would post in the interest mailing list forum)