OpenSceneGraph VS Qt

I started in 2001 with OpenSceneGraph which made extensive use of intrusive pointers. This was 10 years before C++11 note. That codebase continues to be relevant and as performing as ever.

browse github and try to contribute. I started with OpenSceneGraph

I have been using OpenSceneGraph for over 20 years. It is used in the military a lot and I myself have seen it used to simulate war scenarios with realtime data aboard of a command-and-control center of a battleship.

Does http://www.openscenegraph.org/ fit?

Speed Dreams: It is a fork of TORCS, and was born as the need to include many more functions to the latter. In Speed Dreams the menus would be completely redesigned, adding many more options and making them much more intuitive; the game acquired dynamic time, improvements in reflections, career mode, a new simulation mode and multi threading. Over time many more options were implemented, such as local multiplayer mode, Force Feedback, and of course more and better cars and tracks, a new and more powerfull graphic engine (OpenSceneGraph) among other things, making it a much more complete game than its predecessor. They recently they have presented version 2.2.3. You can also install it in AppImage and Flatpak format.

Here is an example: https://github.com/openscenegraph/OpenSceneGraph/blob/master/examples/osgsimplegl3/osgsimplegl3.cpp

openscenegraph (mainly focuses on graphics, used by openmw for example)

Is not little, is very complex open source racing simulator. There are a lot of cars, categories, tracks. The physics has a lot of work . About the graphics, the devs are working on change the graphic engine to OpenSceneGraph, that actually works, but needs much more polishing. You can see his quality on this video: https://youtu.be/4daTgcxEWRg

I love Godot for a complete game engine. For just the renderer you could consider http://www.openscenegraph.org

Qt mono repo : .. you could check out all submodules and simply use CMake to exactly achieve this. A mono repo also means that if I only use qtbase and declarative, I would need to have all submodules in there? - No

For e.g. if you’re writing a framework, you need to interface with Cocoa on MacOS to draw windows, which only provides an Objective C or Swift interface. You can look at the Qt source code and see how they do it: https://github.com/qt/qtbase/tree/067b53864112c084587fa9a507eb4bde3d50a6e1/src/plugins/platforms/cocoa

That's because Qt 6 wholeheartedly converted to CMake for you. (At least it is better than qmake.) In order to support this Qt has this large battery of CMake files [1]. Qt is of course a clear outlier, but you can't expect the same level of support from every other library you want. My points about "anything exotic" still stand.

[1] https://github.com/qt/qtbase/tree/dev/cmake

What are you talking about? Qt has GTK theme support built-in: https://github.com/qt/qtbase/tree/dev/src/plugins/platformthemes/gtk3

This looks like the Qt bug solved by this commit: https://github.com/qt/qtbase/commit/acaabc9108dfe75530960cf8e3ec4f3602cd82e0

Yeah, I'm sure it's completely unheard of. Oh except that it took me all of a couple minutes to find an example of that exact thing in one of the largest, most commonly used C++ frameworks out there.

I don't see any connect in https://github.com/qt/qtbase/blob/dev/src/corelib/tools/qsharedpointer_impl.h, and QPointer isn't a QObject (though I don't know if the latter is actually necessary for signal-slots). One (unreliable) way to test is to see if a QPointer fails to be nulled out when the QObject is blocked by a QSignalBlocker. Alternatively I'd set a data breakpoint on a QPointer and try it out. But I don't have the time right now.