-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
imgui on touchscreen #2650
Comments
Forgot to fill requested issue template, closing. Please fill template and i’ll reopen. |
Hi, i have updated my question. |
The problem is something else. In the Windows event layer, the touch down and touch up events are fired and processed in the same frame. So the event handling logic of ImGui does not encounter it. As a fix, if the touch up is in the same frame as touch down, handling of the touch up should be delayed until the next frame. I have some working code for this if you are still interested (also contains a fix for touch scrolling). |
@bvgastel regarding your fix about scrolling, are you talking about scrolling with the lateral scrollbar on by touch+drag up/down the contents in the middle of the widget, as you would do on a phone? |
In the middle of the widget, just like a phone. |
@bvgastel nice! would you be able to share some code? Thank you |
Closing this specific/old touch issue with should be solved by input trickling introduced in 1.87. |
Hi, not much to add my code here, because it is simple question.
Version/Branch of Dear ImGui:
Version: v1.49
Branch: master
Back-end/Renderer/Compiler/OS
Back-ends: imgui_impl_glfw.cpp
Compiler: vs2017
Operating System: Windows 10 64bit
My Issue/Question:
If i test button with mouse, it clicked with single-click.
But if i test button on touchscreen, it can not be clicked with single-click,
but only double-click.
How i use imgui button on my touchscreen(microsoft surface, win10) with single-click?
Screenshots/Video
Standalone, minimal, complete and verifiable example: (see #2261)
Thanks!
The text was updated successfully, but these errors were encountered: