clarify state changes are not always a change
This commit is contained in:
parent
1fa25d2fd2
commit
965882a5bb
@ -1,6 +1,6 @@
|
||||
# User Interface dev notes
|
||||
|
||||
The primary user interface is implemented in python 3 and targets a 240x240 color LCD for output and four buttons as well as a four direction joystick with another button as user input. It's a simple state machine that interacts with the musikcube api running on the same device. at the end of each state, the display's framebuffer is updated before moving to the next state.
|
||||
The primary user interface is implemented in python 3 and targets a 240x240 color LCD for output and four buttons as well as a four direction joystick with another button as user input. It's a simple state machine that interacts with the musikcube api running on the same device. at the end of each state, the display's framebuffer is updated before moving to the next state (which could be the same as the currrent state).
|
||||
|
||||
## display layout and info
|
||||
the 20 uppermost pixel rows are used for battery state, current time, total time.
|
||||
|
Loading…
Reference in New Issue
Block a user