Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Windows 7 External Touch Screen Issues

I'm running a Roll20 game on an external touchscreen on Windows 7 with chrome. The touch works fine for selecting tokens and opening the side bar and everything else, but touch doesn't seem to work for dragging icons, zooming, anything that doesn't have to do with a single click. Is there any possible solution?
Additionally, the drag option works just fine on a scroll bar. But I can't move tokens or windows around.
External touch screens often have calibration issues. Make sure the external is configured to exactly the same resolution as the main. Try it with other browsers; is the issue specific to Chrome? Beyond that; you have to refer to the touchscreen drivers/manufacturer really.
Well I believe it's more likely an issue on Roll20 or Chrome's side, because using the sliding bars in game works just fine, it's just moving tokens or windows that seems to be a problem. However, it worked just fine on Internet Explorer 11. Still, kind of a bummer.
perhaps it's related to graphics acceleration in Chrome. I don't recall where the setting is specifically (I'm a firefox guy) but you could try disabling that and also try running Chrome in full-screen mode, perhaps. Shots in the dark without something in front of my to poke at.
I'm honestly not sure how Roll20 would interact with that. Windows 7 devices aren't ones that we specifically treat as "touch screens" the way we do for Android or iOS. I'm not sure if Win 7 even triggers "touchstart" "touchend", etc. events like an iOS device would. Unfortunately I don't have a Windows 7 tablet for testing...but I'll look into it and see if I can figure something out. But are you saying that it all works fine in IE11 just not Chrome?
Yes, it worked perfect on IE11, oddly enough