For AI agents: a documentation index is available at /llms.txt. Markdown versions of all pages are available by appending .md to any URL.
Class TwoFingersTouchHandlerAbstract
Hierarchy (View Summary)
- TwoFingersTouchHandler
Implements
Constructors
constructor
-
Returns TwoFingersTouchHandler
Methods
disable
enable
-
Enables the "drag to pitch" interaction.
Parameters
Optionaloptions: boolean | AroundCenterOptions | null
Returns void
isActive
-
Returns a Boolean indicating whether the "drag to pitch" interaction is active, i.e. currently being used.
Returns boolean
trueif the "drag to pitch" interaction is active.
isEnabled
-
Returns a Boolean indicating whether the "drag to pitch" interaction is enabled.
Returns boolean
trueif the "drag to pitch" interaction is enabled.
reset
-
resetcan be called by the manager at any time and must reset everything to it's original stateReturns void
touchcancel
-
Returns void
touchend
-
Parameters
- e: TouchEvent
- points: Point[]
- mapTouches: Touch[]
Returns void
touchmove
-
Parameters
- e: TouchEvent
- points: Point[]
- mapTouches: Touch[]
Returns void | HandlerResult
touchstart
-
Parameters
- e: TouchEvent
- points: Point[]
- mapTouches: Touch[]
Returns void
Handlers interpret dom events and return camera changes that should be applied to the map (
HandlerResults). The camera changes are all deltas. The handler itself should have no knowledge of the map's current state. This makes it easier to merge multiple results and keeps handlers simpler. For example, if there is a mousedown and mousemove, the mousePan handler would return apanDeltaon the mousemove.