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
Hello, i got strange results with docking examples,
maybe something wrong with my setup, i am not sure.
Maybe someone could advise me where start to dig to fix this...
Or maybe i miss stable docking version?
This is a by product of original #2117 issue with multi-viewports, they are programmed with the expectation that window manager honor requested position, and don’t handle it well when it doesn’t. In your case, dear imgui thinks the window is being moved down, but the window manager prevents that from happening, and our docking markers are drawn given expected position of the window. Aside from the markers, the inputs would be broken.
I am expecting to fix that now i have access to a MacOS device exhibiting similar issue.
ocornut
changed the title
docking markers misplaced
Docking markers rendered at wrong location when attempting to move viewports outside of monitor boundaries
Jun 6, 2024
Hello, i got strange results with docking examples,
maybe something wrong with my setup, i am not sure.
Maybe someone could advise me where start to dig to fix this...
Or maybe i miss stable docking version?
Version/Branch of Dear ImGui:
Branch: docking, last commit fdc084f
Back-ends:
imgui_impl_vulkan.cpp + imgui_impl_glfw.cpp
Compiler, OS:
os: linux + X11,
compiler: gcc (Gentoo 13.2.1_p20240210 p14) 13.2.1 20240210
vulkan version 1.3.280, vkinfo.txt
glfw-3.4
Full config/build information:
build default example (need glfw-3.4 sources) with this CMakeLists.txt
Details:
Enable docking, try to move window, docking markers move with window.
Sometimes sub windows lost focus and become hidden behind main window.
Screenshots/Video:
video
video.mp4
Minimal, Complete and Verifiable Example code:
examples/example_glfw_vulkan/main.cpp from repo used
build with cmake --build . --config Debug
The text was updated successfully, but these errors were encountered: