Glasses

Visor can have several pairs set up, and connects to one at a time: the active pair. Every method acts on the active pair. The status needs the state scope; seeing every pair and choosing the active one needs pairs.

Status

visor.glasses.status.collect { status -> }   // now, then each change
val now = visor.glasses.status.first()        // once

A GlassesStatus:

The values come from the glasses, so most are null while they are not connected. Tell models apart by display, never by model, whose wording can change.

Your pairs

Scope: pairs.

visor.glasses.pairs.collect { pairs ->
    pairs.forEach { println("${it.name ?: it.look?.styleName} ${if (it.active) "(active)" else ""}") }
}
visor.glasses.select("2Y0YBYPJ8F007Q")

pairs sends every pair set up in Visor now, then each time one is added, renamed, removed or made active. select makes another pair the active one: Visor lets go of the pair connected now and connects to the new one, as when the person picks it on Visor's home. It returns once Visor has switched, before the pair is connected, so watch status for the link. It fails with busy while a Live view or an import holds the glasses, and with invalid_params and reason not_found for a serial Visor has not set up.

A GlassesPair:

Touches and presses

Scope: inputs. All glasses.

visor.glasses.inputs.collect { input ->
    if (input.source == InputSource.TOUCHPAD && input.action == InputAction.SWIPE_FORWARD) nextPage()
}

Each GlassesInput is one touch of the touchpad or one press of a button, as the glasses report it to the phone. The glasses still act on it as they always do: a tap still pauses the music, and the capture button still takes a photo. The VDK cannot keep an input from them, except back on the Display (below).

A swipe goes forward towards the lenses. touch and release tell when a finger rests on the touchpad and when it leaves; slide_* is a finger that moves while it rests there. time is when Visor heard the input. Which actions a pair reports depends on its model and firmware: treat an action you do not know as unknown, and a source you do not know too.

On the Display the band's gestures come as tap, double_tap, triple_tap, tap_hold and nav_* at any time. While your app shows a layout, the touchpad's come too, and both navigate, as in DAT: nav_*, select and back, and drags with x, y, dx and dy in the glasses' own units. A tap then comes twice, as tap and as select: act on one of them. Ask for some sources only, and keep back for your app, with an InputsRequest:

visor.glasses.inputs(InputsRequest { sources = listOf(InputSource.BAND); keepBack = true }).collect { input -> }

keepBack asks the Display to hand back to your app as back. The band's back, a middle-finger tap, still closes the layout: the Display acts on it before the layout hears it.

Motion

visor.glasses.motion.collect { sample -> }          // 30 samples a second
visor.glasses.motion(rateHz = 60).collect { sample -> }

On the glasses, Visor reads motion from their own sensor service, with nothing on the screen and no toolkit app. The phone fuses the accelerometer, gyroscope and magnetometer into orientation, which settles within two seconds of the start. source is glasses; the band's motion on the wrist is band.motion.

Motion needs the motion scope. The rate is one of 5, 10, 15, 24, 30 or 60 samples a second. A MotionSample:

The axes are Android's, in the sensor's frame. A sensor the glasses did not read for a sample is null.

In a test, wait for fake.glasses.motionRate to be set, then send readings with fake.glasses.motion(ax, ay, az) or a whole MotionSample with fake.glasses.motion(sample).

JSON-RPC

$ visor call glasses.status
{
    "paired": true,
    "link": "connected",
    "serial": "...",
    "display": false,
    "battery": 82,
    "charging": false,
    "worn": true,
    "folded": false,
    "recording": false
}