Skip to content

Alarm #366

@Raupinger

Description

@Raupinger

Now that the timer is basically done its time for the last piece of the triforce, the (un)holy time tool trinity:

The Alarm.

Beyond just putting in the work to build it, I see two main challenges.

  1. Logic
    The timer could simply rely on system timers. Those don't work for longer periods (roll over after 4 hours) and it would be nice to have alarms be persistent in the future. This means we need a daemon regularly checking if an alarm is due. That in turn brings the challenge of not unnecessarily wasting CPU time. I've looked around the docs and think that an endless loop calling vTaskDelay() for one minute would be a decent way to do this. This limits the resolution of timers to a minute, but I don't think that's a big deal.
  2. UI
    In contrast to the stopwatch and timer, a fully featured alarm app cant really be built using one screen. Here are some ideas of what it could look like (Disclaimer: example values may or may not represent values possible in reality :)
    Alarm-concept

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions