I am exploring using dear imgui along side nuklear in an app.
I would like to do this because dear imgui doesn’t have a skinning ability, but nuklear does. This is NOT a game being developed. The app simply has style requirements that dear imgui cannot meet.
For the end user, I want to use nuklear to display the windows using their requested style. But for my purposes, I greatly prefer dear imgui.
The problem I’m having is this: when using both frameworks at the same time, the cursor is not drawn when moving over the nuklear windows. dear imgui seems to be retaining control of rendering the cursor, and since the nuklear window is drawn after the dear imgui windows. If I change the order of drawing, everything is handled properly. So, what about dear imgui is causing it to retain control of the cursor and not allow nuklear to handle the mouse normally?
Also, if I move a nuklear window over a dear imgui window, or vice versa, and then click-n-drag, both windows are moved. I’m pretty sure dear imgui would be able to properly handle not passing on inputs so that only it’s window is manipulated, but is this something that can really be resolved?
Ultimately, what I would like to do is this: setup and render dear imgui first, then allow another GUI framework to be setup and rendered second, without having dear imgui try to retain control of everything going on. Can this be done? Or am I chasing a fools errand?