| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
Cleanup 2078.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Termbox had been taking shortcuts when it thinks the screen hasn't
changed, which doesn't work if some other process messes up the screen.
The Go version has a Sync method in addition to Flush/tb_present for
precisely this eventuality. But it feels like an unnecessary
optimization given C's general speed. Just drop it altogether.
---
This took me a long time to track down, and interestingly I found myself
writing a new tracing primitive before I remembered how to selectively
trace just certain layers during manual tests. I'm scared of generating
traces not because of performance but because of the visual noise. Be
aware of this. I'm going to clean up $log now.
Maybe I should also stop using $print..
|
| |
|
| |
|
|
|
|
| |
Thanks Caleb Couch for bugfixes 2072-2075.
|
| |
|
| |
|
|
|
|
|
| |
Right after I lectured Caleb about not just adding random deltas to make
a program correct, too.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Adjust spaces in 'stash'.
|
|
|
|
| |
Extend deadline for run-interactive.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
If I try to run a single test and it triggers an error the trace gets
saved in the current directory, as if I was trying to log an interactive
run. Then when I try to rerun the test the trace tries to load as mu
code, and hilarity ensues. Just log interactive runs in .traces/ as well.
|
|
|
|
|
| |
Forgot to fix chessboard tests during commit 2022: running sandboxes in
separate routines.
|
| |
|
| |
|
| |
|
|
|
|
| |
Back on a nice cadence of optimizing one case at a time.
|
|
|
|
|
|
|
|
|
| |
Redo some of the work of commits 2025-2032. We still need to create
special-cases for each branch, but we'll now always update cursor in a
single place. We'll also have handle-keyboard-event tell its caller
whether it already took care of rendering or not. That way the caller
only falls back to painting the entire screen when necessary. No more
double-painting.
|
| |
|
|
|
|
| |
Don't render entire screen when appending to line.
|
|
|
|
|
| |
Traces were changing based on whether I was loading a .mu file with
'main' or not.
|
|
|
|
|
|
| |
Mouse clicks towards the right of very wide windows weren't working.
Turns out to be a limitation of the X10 protocol:
https://github.com/nsf/termbox-go/issues/32
|
| |
|
|
|
|
| |
Back to checking render performance everywhere.
|
| |
|
| |
|
|
|
|
|
| |
All scenarios should use just numeric locations, and 'run' should
encapsulate the code under test.
|
|
|
|
|
| |
Standardize on whether screen operations will explicitly write to
'screen' inside scenarios. (Answer: not for setup code, at least.)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Get all tests passing again. Actually slower now than before, thanks to
double-render when editing the sandbox side. But that is temporary.
|
| |
|