about summary refs log tree commit diff stats
path: root/baremetal/504test-screen.mu
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2021-01-22 19:57:33 -0800
committerKartik Agaram <vc@akkartik.com>2021-01-22 19:57:33 -0800
commit121a9eba56d62ef6bd9900bcd771647c0c58e718 (patch)
tree29b19ce63ea7f3e9c733ed847141189e452daf11 /baremetal/504test-screen.mu
parentc316a11ffa6fa184c9c62dc6fccbc0a6aa6c8f63 (diff)
downloadmu-121a9eba56d62ef6bd9900bcd771647c0c58e718.tar.gz
7540 - baremetal: cursor
I spent over a week agonizing over this.

* I had to come to terms with the fact that I don't really know how to
make pixel graphics testable. ASCII art on a pixel by pixel basis feels
inhuman. Just focus on text mode for now.

* I had to set aside the problem of non-English family languages.
Languages like Arabic that can stack complex graphemes together likely
can't be fixed-width. But I don't know enough at the moment to solve for
them.

* I spent a while trying to juggle two cursors, one invisible output
cursor for tracking the most recent print, and one visible one that's
just a hint to the user of what the next keystroke will do. But it looks
like I can fold both into a single cursor. Drawing things updates the
location of the cursor but doesn't display it. Explicitly moving the
cursor displays it, but future drawing can overwrite the cursor.
Diffstat (limited to 'baremetal/504test-screen.mu')
0 files changed, 0 insertions, 0 deletions