Touchmode de-activates the ability to interface with the GUI via a mouse, which is problematic for mixed mode use cases... even when interacting with a touch screen, I'm almost always going to also want to be able to use a mouse as well. I see no reason to deactivate panelexec_interact_mouse_scroll while in Touch mode for example, but I suspect the ultimate solution lies in a unified mode using the mtouchinDAT with Include Mouse activated, possibly combined with a panel chop. I know this gets messy, and is one of the reasons touch developement in TD is so difficult. Just figured I'd report my experience, I think for this to feel good as a touchscreen interface, one needs to be able to adjust slider values with a single click touch interaction. Double clicking will be too difficult to consistently engage an interaction without the logic being confused by subtle movements due to the inaccuracy of a user's second click
Touchmode de-activates the ability to interface with the GUI via a mouse, which is problematic for mixed mode use cases... even when interacting with a touch screen, I'm almost always going to also want to be able to use a mouse as well. I see no reason to deactivate panelexec_interact_mouse_scroll while in Touch mode for example, but I suspect the ultimate solution lies in a unified mode using the mtouchinDAT with Include Mouse activated, possibly combined with a panel chop. I know this gets messy, and is one of the reasons touch developement in TD is so difficult. Just figured I'd report my experience, I think for this to feel good as a touchscreen interface, one needs to be able to adjust slider values with a single click touch interaction. Double clicking will be too difficult to consistently engage an interaction without the logic being confused by subtle movements due to the inaccuracy of a user's second click