Why do some non-touch devices support complications?

They can still consume them, but  things like onPress/exitTo() won't happen. I've been running a publisher/consumer on a fr255 for some time now.  A WF that displays what a widget publishes

By the way, if you don't have a test WF that uses what you publish, I strongly suggest you build one.  On a real device, it don't look like native WF can use what you publish,  It's a bit tricky to find even in a test WF

Thx.  Makes sense.

Here for example is my test WF on the 255 in the sim.  The "widget" that publishes has a background service that runs every 20 minutes and the publishes.  (yes, this works in the sim)

The only thing missing is there is no way to move to the glance without a touchscreen, Everything below the date is what my widget publishes.

It is enough to add to firmware option "send onPress" and allow user to assign it to key combinations so every system 6 device could use complication. But it's better i simpler to remove this functionality...

System 6 devices can use complications right now.  Non-touch devices just can't launch the app that published.

because such decision was made...

ClickType

all this event can be realised by key

Notice "on the screen" in the description.  So only devices with a touch screen

again, just because somebody decide to not emulate by button onPress on non-touch device...