Skip to main content

On screen

While Input.Observer runs, it draws on your screen only when there is something to show: the trail under the pointer while you draw a gesture, a hint naming the action the stroke matches, and messages that actions show. Between gestures nothing is drawn, and clicks always reach the windows you see.

What draws each of these is your choice: Input.Observer's own classic trail, hint window and message window, or the renderer — a plugin such as the Styles plugin, which draws animated trail styles and decorates hints and messages to match. Whatever you choose, gestures, hotkeys and actions work the same.

PageWhat it covers
AppearanceThe Appearance page: theme and language, its sections, what applies at once, sounds, free and purchased styles
Gesture trailsChoosing a trail style, the gallery, each style's settings and preview, Shuffle, a style per draw button, keeping trails light
Hints and messagesWhen the hint appears and what it shows, every hint setting, and how messages from actions look and close
Exclusion zonesAreas of the screen where the buttons and wheel you choose go straight to the window, never starting a gesture

The renderer itself is managed on the Plugins page.

  • Appearance — The Appearance page: theme and language, the gesture trail, hints, on-screen messages, sounds and style packs.
  • Gesture trails — Choosing a trail style, the style gallery, each style's settings and preview, Shuffle, a style per draw button, and keeping trails light.
  • Hints and messages — The hint that names the matching action while you draw, and the on-screen messages actions show: when they appear, how they look and how to change them.
  • Exclusion zones — Areas of the screen where a draw-button press never starts a gesture: drawing zones on the monitor picture, their fields, and what each zone follows.