diff --git a/3rdparty/imgui/CHANGELOG.txt b/3rdparty/imgui/CHANGELOG.txt index 3804190c54..62f2bd20e5 100644 --- a/3rdparty/imgui/CHANGELOG.txt +++ b/3rdparty/imgui/CHANGELOG.txt @@ -39,6 +39,171 @@ HOW TO UPDATE? and API updates have been a little more frequent lately. They are documented below and in imgui.cpp and should not affect all users. - Please report any issue! +----------------------------------------------------------------------- + VERSION 1.92.7 (Released 2026-04-02) +----------------------------------------------------------------------- + +Decorated log and release notes: https://github.com/ocornut/imgui/releases/tag/v1.92.7 + +Breaking Changes: + + - Separator: fixed a legacy quirk where `Separator()` was submitting a zero-height + item for layout purpose, even though it draws a 1-pixel separator. + The fix could affect code e.g. computing height from multiple widgets in order to + allocate vertical space for a footer or multi-line status bar. (#2657, #9263) + The "Console" example had such a bug: + float footer_height = style.ItemSpacing.y + ImGui::GetFrameHeightWithSpacing(); + BeginChild("ScrollingRegion", { 0, -footer_height }); + Should be: + float footer_height = style.ItemSpacing.y + style.SeparatorSize + ImGui::GetFrameHeightWithSpacing(); + BeginChild("ScrollingRegion", { 0, -footer_height }); + When such idiom was used and assuming zero-height Separator, it is likely that + in 1.92.7 the resulting window will have unexpected 1 pixel scrolling range. + - Multi-Select: renamed `ImGuiMultiSelectFlags_SelectOnClick` to `ImGuiMultiSelectFlags_SelectOnAuto`. + Kept inline redirection enum (will obsolete). + - Combo(), ListBox(): commented out legacy signatures which were obsoleted in 1.90 + (Nov 2023), when the getter callback type was changed from: + bool (*getter)(void* user_data, int idx, const char** out_text) + To: + const char* (*getter)(void* user_data, int idx) + +Other Changes: + +- TreeNode: + - Moved `TreeNodeGetOpen()` helper to public API. I was hesitant to make this public + because I intend to provide a more generic and feature-full version, but in the meanwhile + this will do. (#3823, #9251, #7553, #6754, #5423, #2958, #2079, #1947, #1131, #722) + - In 'Demo->Property Editor' demonstrate a way to perform tree clipping by fast-forwarding + through non-visible chunks. (#3823, #9251, #6990, #6042) + Using SetNextItemStorageID() + TreeNodeGetOpen() makes this notably easier than + it was prior to 1.91. +- InputText: + - Shift+Enter in multi-line editor always adds a new line, regardless of + `ImGuiInputTextFlags_CtrlEnterForNewLine` being set or not. (#9239) + - Reworked `io.ConfigInputTextEnterKeepActive` mode so that pressing Enter will + deactivate/reactivate the item in order for e.g. `IsItemDeactivatedAfterEdit()` + signals to be emitted the same way regardless of that setting. (#9001, #9115) + - Fixed a glitch when using `ImGuiInputTextFlags_ElideLeft` where the local x offset + would be incorrect during the deactivation frame. (#9298) + - Fixed a crash introduced in 1.92.6 when handling `ImGuiInputTextFlags_CallbackResize` + in certain situations. (#9174) + - Fixed selection highlight Y1 offset being very slightly off (since 1.92.3). (#9311) [@v-ein] + - InputTextMultiline: fixed an issue introduced in 1.92.3 where line count calculated + for vertical scrollbar range would be +1 when the widget is inactive, word-wrap is + disabled and the text buffer ends with '\n'. Fixed a similar issue related to clipping + large amount of text. + - InputTextMultiline: avoid going through reactivation code and fixed losing revert value + when activating scrollbar. + - InputTextMultiline: fixed an issue where edit buffer wouldn't be reapplied to back + buffer on the `IsItemDeactivatedAfterEdit()` frame. This could create issues when + using the idiom of not applying edits before `IsItemDeactivatedAfterEdit()`. + (#9308, #8915, #8273) +- Tables: + - Allow reordering columns by dragging them in the context menu. (#9312) + - Context menu now presents columns in display order. (#9312) + - Fixed and clarified the behavior of using `TableSetupScrollFreeze()` with columns>1, + and where some of the columns within that range were Hidable. + - Before: `TableSetupScrollFreeze(N, 0)`: include the N left-most visible columns as + part of the scroll freeze. So if you intentionally hide columns