I would highly recommend you avoid relying on the classes in Qt3DExtras. That code is in a grey area - not really "official & supported". It seems to exist only for the examples (which also don't work in some cases) and it's not "real-world" ready. We were told at the beginning that they would be cleaned up and make their way into a supported state, but that never happened.
<rant>These are pieces that would be useful for anyone learning Qt3D or doing something simple. Yet they continue to be incomplete/not well designed/not supported. Of course if it were between these classes and having actual documentation & working examples for Qt3D, I'd take the docs & examples.</rant> Also - if you're using a CI like Travis, Linux distros don't seem to build & include Qt3DExtras, so you have to build it yourself during the CI process. --- Andy Maloney // https://asmaloney.com twitter ~ @asmaloney <https://twitter.com/asmaloney> On Tue, Apr 9, 2019 at 7:36 AM Marcin Musial <[email protected]> wrote: > Hi, > > I tried to use multiple instances of Qt3DExtras::Qt3DWindow, but it looks > like it doesn't work. Only last one created/activated/shown is rendering. > Is it like that in Qt3D? Or maybe I have to do some extra steps to make it > work. > > For a little bit of context: I'm *not* creating multiple "views" like in > Blender/Maya/3Dmax so configuring FrameGraph with Viewports will not work. > I want to archive to have one big scene view and one or more tool window > popups with small thumbnail for preview of some assets. > > Is it possible at all to do with Qt3D or maybe I hit a limits of Qt3D? > > > _______________________________________________ > Interest mailing list > [email protected] > https://lists.qt-project.org/listinfo/interest >
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
