|
From: James T. <ja...@fl...> - 2021-06-03 10:47:40
|
> On 3 Jun 2021, at 11:32, Patrick Callahan <pat...@gm...> wrote: > > Just ran across this and wondered if it could be useful in Flightgear either as an add-on debugging support tool or as a replacement for PUI. > > https://blog.conan.io/2019/06/26/An-introduction-to-the-Dear-ImGui-library.html <https://blog.conan.io/2019/06/26/An-introduction-to-the-Dear-ImGui-library.html> > I did a brief evaluation of it a few months ago as a possibility - we’re also evaluating it in some projects at my day job. The APi is interesting if you’re starting from scratch and only exclusively in C++, but it’s not a great fit for how we define GUIs in FG (via XML/Nasal) : there is no back door that I could find, to access the persistent state of the GUI, or build it up in a data-driven way. So making a mapping to keep our existing GUI XML working (and updating correctly) becomes a bit of a chore. Kind regards, James |