- Home /
Samsung 42" Touch Screen: Touch response issues
Hi, I'm working on a project that will be deployed on a large single-touch screen. The project is comprised of GUI Textures(Buttons) and an Orbit Script to navigate throughout the scene.
The problem I'm encountering is touch recognition of the orbit script, and even the simple mouseorbit script. The GUI Textures work fine when touched, using the OnMouseDown function. So I know the single touch counts as a left mouse click.
I just cannot figure out why the simple MouseOrbit script will not work within the scene... it detects a left mouse button down.
If a mouse is used as an input device, the entire scene works properly! Does anyone know why the 'touch orbit' will not work?
I appreciate any help with this, and I can understand if more details are needed to solve this issue.
Answer by tanoshimi · Jan 08, 2014 at 01:42 PM
If you're creating a system designed for touch input, you can't use OnMouseXXX callbacks - you should use Input.Touches instead. (The fact that a single touch input registers as Input.GetMouseButton(0) is undocumented, and won't help when you try to handle touch gestures, swipes etc. anyway).
I appreciate you advice Tanoshimi. I'll have to dig the project up and try your advice. It's been a while and I can't remember how much further I progressed before switching gears.
Thank you again, and hopefully this helps anyone who may be ambivalent to the input methods while developing touch applications.