diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-07-17 18:19:31 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-07-17 18:19:31 -0700 |
commit | e52972cb0aaa749e901b518c0b594dd14d687fa6 (patch) | |
tree | a6e169f8776912e918e028bd31ce203a2d2152f6 /tangle/030tangle.cc | |
parent | 05d0a12536c97bc043b0bf106de80711bc1f0ab4 (diff) | |
download | mu-e52972cb0aaa749e901b518c0b594dd14d687fa6.tar.gz |
1807 - all tests passing again
Rendering the screen was easy to fix: I'd just never gotten around to printing anything but spaces. Rendering the 'screen:' was harder. Turned out I wasn't incrementing row, and so the screen contents were overwriting the header. Much fiddling with row ensued. Still unclear if I have a sane policy for managing row. I don't leave cursor on start of next line after render-string (relying on run-interactive to return strings terminated by newlines) but I do so in render-screen. Never mind, all architecture is illusion and all programs sit on the edge of chaos. This is just the best way I know how to permit others to periodically reclaim architecture from chaos by expending energy. But it'll never be perfect. Crash-only architecture for the win.
Diffstat (limited to 'tangle/030tangle.cc')
0 files changed, 0 insertions, 0 deletions