about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2022-05-231-1/+2
|
* similar tests for cursor upKartik K. Agaram2022-05-231-1/+67
|
* couple of tests for cursor downKartik K. Agaram2022-05-232-8/+68
|
* bugfix: don't rely on Screen_bottom1 while scrollingKartik K. Agaram2022-05-233-12/+23
| | | | | Setting up the test just right to test the thing I want to test was a rube goldberg machine of constants.
* first successful pagedown test, first bug found by testKartik K. Agaram2022-05-234-14/+86
| | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff.
* first test!Kartik K. Agaram2022-05-222-12/+87
|
* fold variables for screen dimensions into the app frameworkKartik K. Agaram2022-05-221-8/+8
|
* one more implicationKartik K. Agaram2022-05-221-0/+3
|
* basic test-enabled frameworkKartik K. Agaram2022-05-224-34/+251
| | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up.
* renameKartik K. Agaram2022-05-222-1/+3
|
* yet another bugfix. But for how long?Kartik K. Agaram2022-05-221-1/+1
|
* beginnings of a test harnessKartik K. Agaram2022-05-222-0/+38
| | | | | | | | | | | | | | | | | | | I have no fucking idea what I'm doing. All I know is that there's still too many goddamn bugs[1]. Test motherfucking harness or bust. For starters this is just the default love.run from https://love2d.org/wiki/love.run [1] The following file crashes if you repeatedly press cursor-down: << a b c ```lines ``` x >>
* up and down arrow now moving by screen line where possibleKartik K. Agaram2022-05-211-25/+47
| | | | Drawings can't be drawn partially, which sometimes makes things jerky.
* bugfix: printing the first part of a line at the bottom made it seem ↵Kartik K. Agaram2022-05-212-30/+43
| | | | | | non-wrapping Still lots wrong here.
* cleanerKartik K. Agaram2022-05-211-3/+2
|
* I feel confident now that page-down is working.Kartik K. Agaram2022-05-212-3/+12
|
* couple of TODOsKartik K. Agaram2022-05-212-1/+2
|
* beginning of a new approach to scroll+wrapKartik K. Agaram2022-05-212-155/+187
| | | | | | | So far I've just changed how existing variables are organized, and put some scaffolding in place for dealing with the new types. Next up: rewriting the code for scrolling to something that feels more obviously correct.
* bugfix: escape key to hide online helpKartik K. Agaram2022-05-212-6/+6
|
* help tweakKartik K. Agaram2022-05-211-1/+3
|
* show when we're naming a pointKartik K. Agaram2022-05-211-2/+14
|
* support for naming pointsKartik K. Agaram2022-05-217-4/+62
| | | | There's still an absence of affordance showing when you're in naming mode.
* new known issue with drawingsKartik K. Agaram2022-05-211-0/+19
|
* one missing transition between shape modesKartik K. Agaram2022-05-211-1/+3
|
* several bugfixesKartik K. Agaram2022-05-212-2/+9
| | | | All introduced when I built rectangles and squares in commit e27165cb.
* bugfix: rectangles and squares are now savedKartik K. Agaram2022-05-212-2/+11
|
* bugfixKartik K. Agaram2022-05-211-10/+2
| | | | | Looks like I never retested rectangles after I implemented drawing squares, even though I made changes to the rectangle implementation :/
* bugfix: missed rename in one fileKartik K. Agaram2022-05-211-2/+2
|
* disable some debug printsKartik K. Agaram2022-05-201-23/+23
| | | | | I'm still very much in the region where this is valuable sensor data. This is a new domain.
* more precise height calculation when scrolling up as much as possible while ↵Kartik K. Agaram2022-05-201-4/+21
| | | | keeping cursor on screen
* keep cursor on screen when pressing 'down'Kartik K. Agaram2022-05-202-3/+5
|
* renameKartik K. Agaram2022-05-201-7/+7
|
* reduce ambitions a bit: page up/down need not start screen from the middle ↵Kartik K. Agaram2022-05-202-20/+17
| | | | | | of a line But we still have work to do for cursor up/down.
* first stab at equally hacky cursor down supportKartik K. Agaram2022-05-201-11/+42
|
* stop recomputing Cursor_x now that we're saving itKartik K. Agaram2022-05-201-5/+3
|
* clearer commentsKartik K. Agaram2022-05-201-2/+3
|
* ensure Filename is writable when opened outside a terminalKartik K. Agaram2022-05-201-1/+1
| | | | Thanks Jimmy Miller for reporting this.
* some more loggingKartik K. Agaram2022-05-201-1/+11
| | | | | | | | | | | Still lots of signs it's all messed up, but I can't be sure until I bring all the other keyboard shortcuts in sync. I just need a better data structure that simplifies the logic. Perhaps talk in terms of screen lines. In which case: We'll need to convert lines to screen lines at some point. We'll need to fix up screen lines when inserting and deleting characters.
* snapshot - no, that's all wrongKartik K. Agaram2022-05-203-17/+43
| | | | | I've been only thinking about up arrow when cursor is at top of screen. Hopefully this is better.
* another piece of support for line wrapping in cursor upKartik K. Agaram2022-05-202-1/+10
|
* first stab at supporting wrapping in cursor upKartik K. Agaram2022-05-202-13/+33
| | | | Looks pretty clean.
* bugfixKartik K. Agaram2022-05-201-16/+3
| | | | | | | I'd wrapped currx in two conditionals, and not noticed that it gets reclaimed within the other. The hint is clearly more work than it's worth. Just take it out.
* new globals: draw partial screen line up topKartik K. Agaram2022-05-202-2/+9
| | | | | I'm not setting these yet. Rendering seems to be working after manually setting them.
* start using some globalsKartik K. Agaram2022-05-202-6/+6
|
* moveKartik K. Agaram2022-05-201-2/+4
|
* bugfixKartik K. Agaram2022-05-201-1/+1
|
* start remembering where the cursor is drawn in pxKartik K. Agaram2022-05-202-0/+4
| | | | We'll start using this in cursor up/down motions.
* extract a functionKartik K. Agaram2022-05-202-12/+9
|
* moveKartik K. Agaram2022-05-191-35/+35
|
* planning out cursor up/down over wrapped linesKartik K. Agaram2022-05-192-3/+5
|