From 8fd031f1befa17a7dd1d7a7e6d3b8e86a5ce15bd Mon Sep 17 00:00:00 2001 From: omar Date: Wed, 16 Sep 2020 14:52:39 +0200 Subject: [PATCH] Updated Docking (markdown) --- Docking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docking.md b/Docking.md index 35f97a8..037f157 100644 --- a/Docking.md +++ b/Docking.md @@ -19,7 +19,7 @@ There are 4 additional docked related configuration flags in the io structure wh Several advanced features, such as tight interaction with native multi-viewports, or the DockBuilder are still expecting api changes. I am also not particularly happy with how some aspects of the code are current implemented, and considering to maybe rewrite all of docking from scratch a third time! -However, you can benefit from a lot of docking features without being impacted by any of this. **The largest amount of interactions you'll have with the docking system are a user level and not at API level**. By just enabling the config flag above and calling 1-2 functions you can benefit from 90% of Docking features. Even the hypothetical full rewrite of Docking system is not expected to impact most users. API that are most at risk of changing are hidden in `imgui_internal.h` for this reason, and even so, if they do change, we'll make reasonable effort to document the reasoning the update path. +However, you can benefit from a lot of docking features without being impacted by any of this. **The largest amount of interactions you'll have with the docking system are at end-user level and do not require API calls**. By just enabling the config flag above and calling 1-2 functions you can benefit from 90% of Docking features. Even the hypothetical full rewrite of Docking system is not expected to impact most users. API that are most at risk of changing are hidden in `imgui_internal.h` for this reason, and even so, if they do change, we'll make reasonable effort to document the reasoning the update path. In addition, Docking will only move forward with feedback from users, so the more people using it, the closer we are to a reach mergeable version. TL;DR; is totally fine to use for most users.