diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2017-04-16 15:02:42 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2017-04-16 15:05:31 -0700 |
| commit | ace7ffb714ce5314c665f28945ee0f3f1664f9ca (patch) | |
| tree | 191088837e3a6c6fa6a38aae59431efa88c86cb9 /cannot_write_tests_for | |
| parent | ef73b04e744a69973208096a49d4ae52ddbb84d2 (diff) | |
| download | mu-ace7ffb714ce5314c665f28945ee0f3f1664f9ca.tar.gz | |
3824 - experiment: stop buffering in termbox
Now it's much more apparent why things are slow. You can see each repaint happening. Already I fixed one performance bug -- in clear-rest-of-screen. Since this subverts Mu's fake screen there may be bugs. Another salubrious side effect: I've finally internalized that switching to raw mode doesn't have to clear the screen. That was just an artifact of how termbox abstracted operations. Now I can conceive of using termbox to build a repl as well. (I was inspired to poke into termbox internals by http://viewsourcecode.org/snaptoken/kilo and https://github.com/antirez/linenoise)
Diffstat (limited to 'cannot_write_tests_for')
| -rw-r--r-- | cannot_write_tests_for | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/cannot_write_tests_for b/cannot_write_tests_for index 1cdaa20a..5e10fa49 100644 --- a/cannot_write_tests_for +++ b/cannot_write_tests_for @@ -2,11 +2,9 @@ 1. assertion failures or errors inside scenarios 2. screen background color 3. has-more-events? -4. hide/show screen -5. more touch event types -6. sandbox isolation -7. errors in reading/writing files (missing directory, others?) +4. more touch event types +5. sandbox isolation +6. errors in reading/writing files (missing directory, others?) termbox issues are implementation-specific and not worth testing: - whether we clear junk from other processes latency in interpreting low-level escape characters |