<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Aug 2015, at 17:33, Riccardo Corsi <<a href="mailto:riccardo.corsi@kairos3d.it" class="">riccardo.corsi@kairos3d.it</a>> wrote:</div></blockquote></div><br class=""><div class="">Thanks Ricky.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="gmail_default" style="font-family: tahoma, sans-serif;">From my point of view the most desired feature is to be able to integrate a qt scene (a GUI layout or a browser/pdf/svg viewer widget) inside an osg driven application smoothly - i.e. without the need of a Qt application to run as main thread loop, but hiding it as a "slave" somewhere in an osg module/node, to make those widget pluggable in a "regular" osg application.</div></blockquote></div><div class=""><div class="gmail_default" style="font-family: tahoma, sans-serif;"><br class=""></div></div><div class="gmail_default" style="font-family: tahoma, sans-serif;"><br class=""></div><div class="">As someone else pointed out, this is a less common scenario for what I’m trying to support. What I care more about is people who want to use Qt for the thing it’s good at, and integrate OSG within it. So they typically want menus, dialogs etc from QWidgets or QQ2 (potentially including Qt Quick Controls). That’s the use case I’m focusing on for now.</div><div class=""><br class=""></div><div class="">Hiding Qt introduces a lot of complexity and also trades that rather detailed, tailored Qt event loops on each platform, for the rather basic ones in each of the GraphicsWindow subclasses. </div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="gmail_default" style="font-family: tahoma, sans-serif;">Instead if you're interested, a while ago I coded an integration to render with osg inside a QtQuick+QML application.</div><div class="gmail_default" style="font-family: tahoma, sans-serif;">Basically the solution implements a custom QtQuick node which renders an osgViewer scene to an FBO, and then copies the FBO contents back to the Qt context, to make it available in the qt/qml scenegraph which renders the widgets.</div><div class="gmail_default" style="font-family: tahoma, sans-serif;">The osgQuickNode uses a separate OpenGL context, not to interfere with the one used by Qt for its own scene rendering. </div><div class="gmail_default" style="font-family: tahoma, sans-serif;">All the code is here: <a href="https://github.com/rickyviking/qmlosg" target="_blank" class="">https://github.com/rickyviking/qmlosg</a></div><div class="gmail_default" style="font-family: tahoma, sans-serif;">If you have questions about the implementation feel free to write me.</div></blockquote><br class=""></div><div class="">The solution you propose of a custom QtQuick node rendering OSG is definitely interesting to me, and I would guess your code is likely 90% the same as what I would write, so with your permission I might attempt to merge it with my submission, once I have time to review it.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class="">James</div></body></html>