Bug - Hybrid touchscreen with mouse support - Need to disable Touch
I finally figured out why I couldn't navigate between slides in edit mode... Because I found the same problem in "Present" mode.
Your implementation for Touch is either/or, never <and>.
When a touchscreen is detected, Touch is enabled and <disables> mouse clicks.
Recommend:
Although existing media detection can remain the same (I suspect is part of one of the Frameworks you are using so may be difficult to customize anyway), there should be a way to disable Touch specifically (ie with a checkbox that sets the touch attribute to false).
For now, anyone who follows in my footsteps where you either have a hybrid laptop with touchscreen, or add a touchscreen to your ordinary system with mouse, the workaround is to tap the screen whenever you hover over an object and see a possible clickable action (eg. cursor changes) but nothing happens when clicked.
Not supported in Edit mode, but when in "Present" mode although navigational clicks do not work, hot keys do navigate between slides.
Particularly for my device (HP Envy Touchsmart 17), hybrid support is unusually implemented through hardware which means that hardware fundamentally implements click events by default and <through hardware> (does not require special software drivers) also translates touch events into click events. This is different than typical touch only devices (eg Tablets and mobile phones).
Because of this, if touch is disabled then click events would be returned and I would also not lose the ability to also use Touch.
Curiously, not all objects are affected by this bug. Some objects like re-arranging slides respond to clicks but now I'm wondering if those clicks are being interpreted correctly. Menus also respond to clicks.
But, the navigational arrows in the bottom right of each slide are definitely a problem. If you can identify which framework that object comes from, that is the specific Framework that needs to be Touch disabled for sure.
We used to listen to both click and touch events but a bug fix for Android we rolled out a few days ago broke that. We’ve gone ahead and updated the implementation so that we still listen for both touch and click events for all systems except Android.
-
Tony Su commented
I can verify the problem has been fixed.
Good Show!