I've understood that (experimental) support for Direct3D has been dropped . But what does this mean? Does it mean that the plan was that Qt optionally would do all drawing with Direct3D under Windows, and now it's not going to be like that? Or does it mean that there won't be any Direct3D equivalent to QGLWidget?
It looks like QGLWidget is quite a thick binding to OpenGL. It's fully integrated with the rest of Qt and you can for example draw with Qpainter in a QGLWidget. Lets assume you don't require quite that much for Direct3D. You would be satisfied with a much thinner binding that would coexist with Qt but with a bare minimum of integration. What would be the least effort to accomplish that and what would be the best strategy to accomplish it. Qq is open source so maybe there's even an initiative going on to develop a "QD3DWidget"?
I guess it would be most natural to inherit QWidget and try to somehow get hold of the underlying Win32 window. One probably could reuse much of the QGLWidget implementation. I note that Qt can interoperate with ActiveX. Could that be a better approach?
If I go for Qt I'm going to use OpenGL. After all, portability is one of the major reasons for using Qt in the first place. The reason I'm asking is that I would feel more comfortable with a fall-back strategy in place. Direct3D has a strong presence and isn't going away anytime soon. I may never use it but I would like some indication as to what effort would be involved if I have to. This would also give an indication of how extendible Qt is.
Thank you.
Bookmarks