UGTK / Toolkit / Mobile / GestureSystem Completed

Gesture System

Summary

The Gesture System recognises taps, double taps, long presses, swipes in the four directions and pinch in/out, and exposes each of them as UnityEvents you wire from the inspector.

Two managers implement the same set of events: one reads the mouse, the other reads touch. The game logic listens to the same events either way, so a build can be tested on the desktop and shipped on mobile without changing a single listener.

Content

• Modules Dependencies
• Setup
• How To Use
• The Events
• Testing Scene
• Technical Info

Modules Dependencies

• Event System: optional. Assign a Mn_ZeroParametersController and each gesture also raises a named event through it, so listeners can be wired by name instead of by reference.

Setup

Drop the manager that matches the platform: DesktopGestureManager for mouse, MobileGestureManager for touch:

Tune the thresholds — how long a double click may take, how long a press must last to count as a long press, how many pixels make a swipe:

Optionally associate a Mn_ZeroParametersController, to route the gestures through the Event System as well:

How To Use

Wire the events in the inspector, or subscribe from code on the instance you put in the scene — there is no singleton and no static accessor:

[SerializeField] private Mn_Abstract_GestureManager gestures;

void OnEnable()
{
    gestures.onTap.AddListener(OnTap);                 // Vector2: where
    gestures.onSwipingRight.AddListener(OnSwipeRight); // Vector2 start, Vector2 current
    gestures.onPinchingOut.AddListener(OnZoom);        // float: the delta
}

Good to know:

• Every gesture comes in three moments: …Start, the continuous …ing…, and …End. Use Start to begin a preview, the continuous one to follow the finger, End to commit. A swipe handled only on End feels unresponsive.
• The two managers are not interchangeable at runtime. Pick the one for the platform (or swap the prefab per build); nothing detects the device for you.
• The thresholds decide the feel. Too low a swipeThreshold turns every sloppy tap into a swipe; too high and short swipes are lost.
• The press threshold gates the continuous event, not the start. onPressingStart fires as soon as the button goes down; onPressing only begins once the press has lasted pressThreshold. So "has this become a long press?" is answered by the first onPressing, not by onPressingStart. Both managers behave this way — until 2026-07-30 the desktop one ignored the threshold entirely and reported every click as a hold.
• Pinch needs two touches, so it never fires on the desktop manager.
• There is no filtering over the UI: a gesture is recognised even when it starts on a button. Check EventSystem.current.IsPointerOverGameObject() in your handler if the UI must swallow it.
• The coordinates are screen pixels. Convert with ScreenToWorldPoint before comparing them to anything in the world.

The Events

Testing Scene

Open Scene/GestureSceneExample.unity and press Play: every recognised gesture is reported, so the thresholds can be tuned while watching the result.

Technical Info

• Back to the toolkit index

© 2026 Marcello De Bonis. All rights reserved

More in Mobile.

all 2 →

Motion System

Accesses and normalizes device motion/accelerometer data for gameplay and UI effects.

Completed