Skip to content

Consistent input controls design #631

@tracygardner

Description

@tracygardner

Consistent input controls design: Shared behaviour patterns across keyboard, touch and controllers.

  • Refactor and improve existing input handing for buttons
  • Clickable object discovery on mobile/touch/keyboard. You get a cursor change on desktop but this isn't visible to other users. Interactable icon added to closest interactable object for free camera and player following camera.
  • On click behaviour for games controllers? Should this be like E in some platforms where getting close to an object pops up an option. Should we map to an existing key so it works with one of the game controller buttons? Key mappings
  • On click behaviour for keyboard users. Do they need a way to move the cursor or an alternative like E? Went with an alternative like E to avoid the need to have a cursor in the center of the screen.
  • Refactor and improve existing camera behaviour
  • Moving the babylon js camera when on touchscreen. Add buttons for full interaction. (Page up / down etc on desktop)
  • Test adaptive input devices

Metadata

Metadata

Labels

No labels
No labels

Type

No fields configured for Task.

Projects

Status
Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions