-
-
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
Offset tooltip and drag/drop position for touch based input #8036
Comments
it is not incorrect, but I think the issue you are pointing at would be best corrected in the library itself and by default, so we should investigate that.
You could technically call |
It's not as simple as expected for a surprising reason: using a position pivot that is not (0,0) make it visible and problematic when a tooltip change from one another, e.g. color preview tooltip vs color drag tooltip. I'll need more time to fix it nicely. To clarify: if the tooltip size changes then it affects the position using pivot, so there is a visible glitches where you see the new tooltip in one position then another the next frame. |
I have pushed f057541, 014b722 and 5109a77. Also amended test: ocornut/imgui_test_engine@5f61301 Let me know if that works for you! |
This broke positioning of tooltip when using keyboard/gamepad navigation. |
Fixed with 50de550 |
Version/Branch of Dear ImGui:
docking
Back-ends:
imgui_impl_android.cpp + imgui_impl_opengl3.cpp
Compiler, OS:
ndk, Android
Full config/build information:
No response
Details:
because the content of the tooltip is kind of hard to see if the input is touch based (blocked by finger), i would like to offset the tooltip position.
right now im using this code
is this the correct way? im also using this with
BeginDragDropSource
, however, the drop target location remain in the touch position, which again is kind of blocked by the finger, so is it possible to also offset theBeginDragDropTarget
accept position?Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response
The text was updated successfully, but these errors were encountered: