You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
request a render when WpmUpdateEvent changes the display context
add a driver-selected sleep transition: render a final sleeping frame or enter sleep immediately
add a default no-op driver hook for entering and leaving the sleeping state
correct the documented default minimum render interval from 10 ms to 33 ms
Why
DisplayProcessor subscribed to WPM updates but only changed RenderContext::wpm. In event-driven mode, the displayed value could remain stale until an unrelated event arrived. WpmProcessor samples once per second and publishes only when the value changes, so this does not add per-key notifications; the existing 33 ms render coalescing still applies.
Displays also need different sleep transitions. E-paper or memory displays may render and flush a final special frame, while a power-managed OLED may turn off without transferring another framebuffer. DisplaySleepBehavior makes that choice explicit:
RenderThenSleep (default): render and flush the sleeping context, then call set_sleeping(true)
SleepImmediately: skip the final render and call set_sleeping(true) directly
On wake, set_sleeping(false) runs before the next render. This defines display preparation around RMK's existing sleep event without attempting to define platform deep-sleep policy.
The need was found while adapting an existing downstream OLED backend, which keeps its board-specific power, dirty-page, and error handling.
Compatibility
Both new DisplayDriver methods have defaults. Existing drivers and renderers require no changes, and the default preserves the current built-in renderer behavior.
hitsmaxft
changed the title
fix(display): reliably redraw state changes
fix(display): render WPM and handle sleep transitions
Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
WpmUpdateEventchanges the display contextWhy
DisplayProcessorsubscribed to WPM updates but only changedRenderContext::wpm. In event-driven mode, the displayed value could remain stale until an unrelated event arrived.WpmProcessorsamples once per second and publishes only when the value changes, so this does not add per-key notifications; the existing 33 ms render coalescing still applies.Displays also need different sleep transitions. E-paper or memory displays may render and flush a final special frame, while a power-managed OLED may turn off without transferring another framebuffer.
DisplaySleepBehaviormakes that choice explicit:RenderThenSleep(default): render and flush the sleeping context, then callset_sleeping(true)SleepImmediately: skip the final render and callset_sleeping(true)directlyOn wake,
set_sleeping(false)runs before the next render. This defines display preparation around RMK's existing sleep event without attempting to define platform deep-sleep policy.The need was found while adapting an existing downstream OLED backend, which keeps its board-specific power, dirty-page, and error handling.
Compatibility
Both new
DisplayDrivermethods have defaults. Existing drivers and renderers require no changes, and the default preserves the current built-in renderer behavior.Validation
displayand-D warningsthumbv6m-none-eabi