Make classes not depend on the implicit GImGui context (#6199, #5856, #6199): ImGuiIO

Browse source

This commit is a preparation toward adding ImGui apis with explicit context
and making ImGui applications being able to use multiple context at the same time
whatever their concurrency model.

About ImGuiIO:
- ImGuiIO depends on ImGuiContext because some of its method want to event to `g.InputEventQueue`.
- To make ImGuiIO aware of the context to use, context which creates the ImGuiIO is given as argument of ImGuiIO constructor.
- The assert `IM_ASSERT(&g.IO == this && "Can only add events to current context.")` has been removed since it does not make sense anymore

NOTE: ImGuiIO could be completely independent of ImGuiContext if the InputEventQueue was moved from ImGuiContext to ImGuiIO, but since
ImGuiIO is a public class it would expose InputEvent type. Solving this problem is out of the current scope, but it is interesting to notice.

...

This commit is contained in:

Marc Delorme 2022-11-01 20:35:05 +09:00 • committed by ocornut

parent 5a1e6b60a2

commit 10ace228bc

4 changed files with 20 additions and 15 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

docs/CHANGELOG.txt

View file

24

imgui.cpp

View file

2

imgui.h

View file

8

imgui_internal.h

View file