Feature discussion: [Alarm/sched] Improve snoozing

[thyttan]

I've been wanting a more fleshed out snoozing experience.

AFAIK today we can adjust the length of snoozing in the sched settings and this applies equally to all alarms/timers/etc. In some situations this feels a bit clunky to me. A short timer for when I'm cooking may not beg for the same length snooze as is appropriate when waking up by an alarm.

Some ideas:

• when pressing "Snooze" open a new prompt with up to four options for length.
• treat snoozing for timers differently to alarms and events
  • add a separate snooze for timers setting
    • in addition to fixed length snooze add possibility to have snooze length be set as some fraction of the timer length in question.

Please suggest other ideas as well :)

[RKBoss6]

Is there a way to detect a long-press of the button? If so, a long press can open up the snooze menu, and a regular press snoozes for the default time set.

[thyttan]

@RKBoss6 I think that would be a simple and elegant solution! I don't know if showPrompt propagates long press information. If not we could possibly add that.

[thyttan]

What should the four snooze options be in the snooze prompt?

Suggestions:

1. Both Alarms and timers (etc) has the same fixed options: 1, 5, 10 and 20 minutes.
2. • Alarms: 1, 5, 10, 20 minutes.
   • Timers: 10, 20, 50 or 100 % of the timer length in question.

Or some other combination?

[bobrippling]

I think we make it configurable and default to those ⬆

For long-press, we can probably showPrompt but have a setWatch listening for a long press and that listener will cancel the prompt (via a Bangle.setUI())

[thyttan]

But we're talking about the software button right? So rather Bangle.prependListener("touch", ... ) instead of setWatch.

[RKBoss6]

Yes, I was imagining the hold for the software button. How would we go about doing that? I am somewhat new to the bangle.js workspace, so if anyone knows goes to achieve this, drop a reply.

[bobrippling]

We can't listen for a long press on showPrompt - the functionality isn't there, but using a listener on the screen in general would work - we'd want a "touch" handler:

Bangle.prependListener("touch", (_btn, xy) => {
  if (xy.type === 2) {
    // long press - show the snooze menu
  }
})

[thyttan]

Yes and we could even limit it to the area of the snooze button 👍I think that would be neat.

Edit: And we'll want a E.stopEventPropagation() as well.

[RKBoss6]

Hey! Just a quick update, I was working on this, but my bangle is currently out for the count, so it doesn't really work right now... You guys seem like you know a lot about touch listeners, so any help on that front would be really useful (I hadn't even heard of touch listeners before this issue so...).

That'll just help me get through this quicker when my bangle is back... Thanks!

[thyttan]

I suggest we extend showPrompt to accept two actions per button. That feels more maintainable than having the add-on touch listener.

It needs to be backwards compatible not break for older firmwares but that shouldn't be an issue.

Maybe make:

• options.buttonsLong hold long press actions.
  • needs to use same name keys as options.buttons.
• if button is long-pressed and corresponding entry exist in options.buttonsLong then trigger it.
  • else do exactly what the current implementation does today.

Happy to put that into code and then you could just use that in your update to sched @RKBoss6!

@gfwilliams would a PR with that tweak to showPrompt_Q3 on espruino/Espruino be ok?

[RKBoss6]

@thyttan If you can add that to showPrompt, that would be great! I would suggest if you do that and @gfwilliams approves, also do that to showAlert, or anything else that uses a button like that, just for consistency...

[RKBoss6]

Although, when we do merge this, users will need the latest cutting-edge firmware for it to work. Maybe we can just add a check for compatibility, and if not present, just keep default snooze behavior... If the fw supports the long press, then use the new snooze menu.

[thyttan]

The way I intend to tweak showPrompt that should be taken care of there automatically 😇

[bobrippling]

I suggest we extend showPrompt to accept two actions per button

Sounds like a plan!

• options.buttonsLong hold long press actions.
  • needs to use same name keys as options.buttons.
• if button is long-pressed and corresponding entry exist in options.buttonsLong then trigger it.
  • else do exactly what the current implementation does today.

I like it - then the user holds onto the options object for a === check, or they pop extra keys in there to distinguish it from a normal tap?