You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ocornut
changed the title
Unexpected DragFloatRange2 draw result in new Tables API cell
Unexpected column's ItemWidth when using multi-components widgets in Tables API cell
Jan 27, 2021
ocornut
changed the title
Unexpected column's ItemWidth when using multi-components widgets in Tables API cell
Tables: unexpected column's ItemWidth when using PushItemWidth/PopItemWidth or multi-components widgets
Jan 27, 2021
…per-colum ItemWidth correctly. (#3760) rework local stacks to facilitate modifying current value without altering the stack.
May consider doing the same for ItemFlags and moving to g.ItemFlags...
Version/Branch of Dear ImGui:
Version: 1.80 via Conan, 1.81 WIP via git clone just now
Branch: master
Back-end/Renderer/Compiler/OS
Back-ends: imgui_impl_glfw.cpp + imgui_impl_opengl3.cpp
Compiler: Clang 11.0.1
Operating System: Arch Linux
My Issue/Question:
Experienced unexpected draw result with ImGui::DragFloatRange2() while testing the new (very nice) Tables API.
In the upper part of the left window is the new tables implementation. The lower part is the same content using the previous Columns API.
The smaller window on the right is the MCVE code below.
Issue occurs using any of the three table layout methods described in imgui_demo.cpp beginning at line 3477.
Screenshots/Video
Standalone, minimal, complete and verifiable example:
Thank you for this excellent UI library. It is a pleasure to use.
The text was updated successfully, but these errors were encountered: