-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overlapped item gets click - even with SetItemAllowOverlap #6512
Comments
I believe my example in the linked comment is incorrect. Low-level
As designed, I believe I believe this needs to be redesigned into, e.g. at minimum a |
Sorry it was too hasty to me to say that when it's not that simple. Prior to 1.89 the code in #3909 (comment) + all descriptions of behavior were fully accurate. In 1.89 we internally started using a system for input-ownership (which wasn't really publicly advertised as a whole, but part of it was used in answers to specific problem). The way this system work broke the behavior of said snippet. |
From my point-of-view as a new Imgui-user, I expected that - by default - all subsequent widgets would take precedence when it comes to handling events. And in case this is not what the user wants, some kind of Anyways, thanks for your help. |
…AllowtemOverlap in TableUpdateBorders(). (#6512, #3909) This was copied from SplitterBehavior(). The only hypothetical value in SplitterBehavior() would be ability to manually call SetItemAllowOverlap() after the call. Btw generally AllowOverlap is undesirable for columns as e.g. a spanning selectable would cover entire width and prevent columns from being used. # Conflicts: # imgui_tables.cpp
Following the recent discovery that an underlying major change in 1.89 broke use of Changelog:
Commits
I have also updated ImPlot accordingly: epezent/implot#486 |
Version/Branch of Dear ImGui:
Version: 1.89.7 WIP
Branch: master
Back-end/Renderer/Compiler/OS
Back-ends: imgui_impl_opengl2.cpp + imgui_impl_sdl2.cpp
Compiler: gcc 13.1.1
Operating System: Linux
My Issue/Question:
I tried the example given in #3909 (comment) with
SetItemAllowOverlap
after button 1, but unlike stated in the comment, when clicking into the intersection of both buttons, button 1 registers the click - not button 2. Did I miss anything?The text was updated successfully, but these errors were encountered: