Touch camera gestures #24
Labels
No labels
area/ai
area/build
area/character
area/combat
area/data
area/docs
area/game
area/net
area/ui
area/world
size
l
size
m
size
s
type
bug
type
design
type
feature
type
refactor
type
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
icub3d/terra-redux-org#24
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
MissionCamerabinds right-drag to orbit and middle-drag to pan, because left was leftfree for selection. A touchscreen has one button, so the camera is currently
uncontrollable on a tablet.
Add a gesture model: one finger to orbit, two to pan, pinch to zoom.
MissionCamerabeing four numbers (focus, yaw, pitch, distance) with aTransformderived from them each frame keeps this a change to how the numbers are driven rather
than a rewrite of the camera.
The hard part
A drag that starts on a unit and a drag that starts on empty ground have to mean
different things, or selection and camera control fight each other. Decide that
explicitly rather than discovering it — a tap-versus-drag threshold, or a rule about
what the gesture started over.
Depends on the input model in
ADR 0003.
Done when
The camera can be orbited, panned, and zoomed on the tablet without interfering with
selecting a unit, and the mouse bindings still work on desktop.