imgui VS GTK+

There are plenty of other GUI libraries out there, and the most common and ubiquitous ones all have extensive documentation, tutorials, or at least examples. Something like Dear ImGui kind of expects you to know GUI programming already, they cater to a more advanced GUI developer.

Besides 3D programming work you are also welcome to improve upon tools like our installer, or help with the UX design of Reshade. We use Dear ImGui. The documentation could probably also need more work.

Off topic -> but on topic of the original post. Do you know if https://github.com/ocornut/imgui is available for embedded? It might be too much but it for a reasonably capable system it's better than web or some high powered UI like Qt.

> I loved the fact Qt had it's own standard library, I know some c++ purists won't like that and the qmake , but we need to understand how many platforms Qt targeted and that the col new C++ features were not there on all this platforms when Qt4 was created

Indeed so! Qt is living today with the fact that it was built and designed long before C++11 was really a thing (where C++11 is the baseline of modern C++ and I would argue that even C++17 should be considered the baseline). The design decisions of Qt are directly against modern C++ design. I think that's ultimately the core of the problem: that modern Qt is orthogonal, not complementary, to modern C++.

Range-for loop? Oops, accidentally detached and deep-copied into a temporary.

Move objects? Just, no.

unique_ptr? Nah, QScopedPointer. Also still not moveable. make_unique? Nah, reset(new...) and ignore the modern advice that you shouldn't use `new`

Qt still takes naked pointers and decides willy-nilly whether to take ownership. It still has examples everywhere for using naked new without even mentioning the context of a smart pointer. It has the concept of "you used new, but the parent actually owns it, unless the parent is null" which is just a time bomb for anyone new to the framework let alone the language.

No, there's no way I would recommend Qt to someone who isn't experienced. Since I wouldn't recommend it then it's no wonder to me why Qt isn't used so much. It has little to do with C++ and a lot more to do with the design decisions of Qt itself.

> IMO the reason Qt is not used as much is because it uses C++

Arguably. Also arguably is because Qt brings along a lot of unnecessary baggage. You mentioned using Qt requires using qmake (which definitely counts as arcane, if not archaic); cmake does a pretty good job of wrapping qmake but doesn't eliminate it. And all of that is because of Qt's non-standard magical signals & slots system which is really just a more error-prone semi-async system when compared to any other eventing system.

Using Qt efficiently strongly needs Qt Creator which isn't nearly as good as Visual Studio or VS Code and not as feature-rich as CLion or other intellij-based IDEs I've used -- but at least it performans way better than CLion or intellij trash.

Qt's license changing in 5.15 has also become a significant penalty to non-commercial use. This fact alone means there's no way I'd use Qt in a new project, even a commercial one.

Modern Qt developers also have to become javascript developers since Qt's UI is heavily driving towards QML. That's an unfortunate direction and also inhibits adoption of Qt IMO. Why write an application in C++ if you need to learn javascript anyway? There are better feature-rich javascript frameworks with better community adoption and better price points.

> what would you use today if you need to make an application for someone, something simple like some buttons, menus and it does a bit of work maybe with some files or the internet), the goal is to be fast and have very few bugs that you will have to support by fixing them

For GUI, Dear Imgui [0].

For network, Asio [1].

For files, plain standard streams. They're not fast but if your files are your bottleneck then I'd consider memory-mapped files.

[0]: https://github.com/ocornut/imgui

[1]: https://www.boost.org/doc/libs/1_77_0/doc/html/boost_asio/re...

ImGui has a docking branch.

Have you tried using a dear imgui template for your tech stack? example_glfw_opengl3 should get you running.

If you want to make a gui program using C++, you could try using DearIMGUI. https://github.com/ocornut/imgui

There are many options but I believe the most popular paradigm is to use immediate mode UIs, like Dear ImGui, and hook them into the rendering engine itself (i.e. translating the UI draw calls to DirectX / Vulkan), with custom textures/fonts/etc. to make the UI feel 'native' to the game.

in '~/.config/gtk-3.0/gtk.css' file. Please note this may break some apps somehow. Also, this is not solution, it's only a workaround. It's better to communicate with GTK developers here: https://gitlab.gnome.org/GNOME/gtk

Yeah, that's the Gtk file dialog. Please file a bug report at https://gitlab.gnome.org/GNOME/gtk.

I'm trying to make a text editor in gtk (yes I know there are already plenty of those, but it is a project to learn, not for actual use), and I got pretty far already I would think. I'm basically following the GTK docs for GTK4 and cross checking them with the examples from the GTK git. However I am stuck on something. The current most state of my program is broken, as I get this error when trying to start the program:

I think you should make a bug report in https://gitlab.gnome.org/GNOME/gtk and ping the author of the blog post (as he's likely concerned about this feature) - I think he's Matthias Clasen (you'll find him easily in gtk contributors or gitlab users).

The first three questions are going to be answered by the documentation or the code itself, (not the thing they call docs on their website.

I have never tested that, but according to the code in GDK (X11, Wayland) looks like set_pointer_emulated() is called on compatibility scroll events. Maybe looking through the code may give more insights

Try calling gdk_event_get_pointer_emulated. It's implemented for scroll events, too: https://github.com/GNOME/gtk/blob/master/gdk/gdkevents.c#L874