I'm looking at creating a Wear OS app for <https://github.com/joreilly/chip-8>. What would be appro...

# compose-wear

[John O'Reilly]

I'm looking at creating a Wear OS app for https://github.com/joreilly/chip-8. What would be appropriate input events to use for moving left/right in example like this?

[Ataul Munim]

Rotary input. I would also include pointer input and move based on which half of the screen the user taps

[John O'Reilly]

I'm using detectTapGestures onPress right now to fire

[Ataul Munim]

You'll be quite limited 😅 perhaps fire could be reserved in the top portion of the screen?

[Ataul Munim]

Or could experiment with gestures like fling up to fire.

[John O'Reilly]

or maybe use onDoubleTap for fire

[Ataul Munim]

Yep. One thing that was annoying for double tap to fire if you're using onPress to move is the slight false trigger; you'd need logic to wait for the double tap to elapse before detecting onPress

[John O'Reilly]

ok, thanks, I'll experiment with a few approaches

[John O'Reilly]

the other option is to go back to showing buttons on screen as is case with other clients in this project

[Ataul Munim]

Yep, it's common on phone based emulators too - semi transparent buttons overlaid on the screen

[yschimke]

Awesome

[yschimke]

I would consider RSB/Bezel to be almost guaranteed on modern watches. At least I think recent devices all have.

[yschimke]

If you sre generating discrete move events like a button press, you might want to use the volume modifier from horologist

[John O'Reilly]

Thanks, will take a look at that

[yschimke]

This one https://github.com/google/horologist/blob/f54be92cc52c6224f88ac401aeee28e1e324a053[…]orologist/compose/rotaryinput/AccumulatedRotaryInputModifier.kt

[louiscad]

Accelerometer + a tap to reset horizon to current orientation could work well.