monome / monome/teletype

New Event Scheduler

Open
#112 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
222
Forks
94
PR merge metrics
No merged PRs in 30d

Description

The AT (now R for repeat) feature requires a new scheduler to be implemented to prevent the inrush of equal-delay scripts from bogging down tele_tick(), causing i2c, trigger, slew, and display problems.

I propose a high-resolution priority scheduler to allow accurate synchronous events and fast response to asynchronous events.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing tele_tick() and the handling of i2c, trigger, slew, and display events to understand where equal-delay scripts cause inrush. Define the scheduler's priority, timing, and synchronous/asynchronous behavior before identifying implementation and verification points; done means those event paths remain responsive under the described load.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.