Conversation
|
So what's the actual reason to push this? Are there any new features you really need? |
|
The big one for me is the feature-rich tables API. Very powerful for creating monitors and control panels for lots of elements/devices/agents etc. The previous columns API was rather clunky. There are also options to view-clip large lists. Other than that I've been inconvenienced more frequently by small quirks and issues that were addressed in later versions. |
|
Thanks for the clarification, makes sense; I'm currently working on a lot of GUI specific code, probably good to merge this change into NAP and use that as a base instead of our current version of |
napimguiandnap::ImGuiServiceto deal with the increased responsibility over input management on the ImGui side.There are a few breaking changes in the ImGui API, but they are well documented. Instances of commonly used functions include:
ImGui::SliderFloatImGui::InputFloatImGui::GetKeyIndex