| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | similar tests for cursor up | Kartik K. Agaram | 2022-05-23 | 1 | -1/+67 |
| | | |||||
| * | couple of tests for cursor down | Kartik K. Agaram | 2022-05-23 | 1 | -6/+66 |
| | | |||||
| * | bugfix: don't rely on Screen_bottom1 while scrolling | Kartik K. Agaram | 2022-05-23 | 1 | -10/+18 |
| | | | | | | 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 test | Kartik K. Agaram | 2022-05-23 | 1 | -3/+58 |
| | | | | | | | | | | | | | | | | | | | | 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. Agaram | 2022-05-22 | 1 | -12/+31 |
| | | |||||
| * | yet another bugfix. But for how long? | Kartik K. Agaram | 2022-05-22 | 1 | -1/+1 |
| | | |||||
| * | up and down arrow now moving by screen line where possible | Kartik K. Agaram | 2022-05-21 | 1 | -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. Agaram | 2022-05-21 | 1 | -21/+26 |
| | | | | | | | non-wrapping Still lots wrong here. | ||||
| * | cleaner | Kartik K. Agaram | 2022-05-21 | 1 | -3/+2 |
| | | |||||
| * | I feel confident now that page-down is working. | Kartik K. Agaram | 2022-05-21 | 1 | -1/+9 |
| | | |||||
| * | couple of TODOs | Kartik K. Agaram | 2022-05-21 | 1 | -1/+1 |
| | | |||||
| * | beginning of a new approach to scroll+wrap | Kartik K. Agaram | 2022-05-21 | 1 | -130/+156 |
| | | | | | | | | 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. | ||||
| * | support for naming points | Kartik K. Agaram | 2022-05-21 | 1 | -3/+1 |
| | | | | | There's still an absence of affordance showing when you're in naming mode. | ||||
| * | disable some debug prints | Kartik K. Agaram | 2022-05-20 | 1 | -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. Agaram | 2022-05-20 | 1 | -4/+21 |
| | | | | | keeping cursor on screen | ||||
| * | keep cursor on screen when pressing 'down' | Kartik K. Agaram | 2022-05-20 | 1 | -2/+4 |
| | | |||||
| * | rename | Kartik K. Agaram | 2022-05-20 | 1 | -7/+7 |
| | | |||||
| * | reduce ambitions a bit: page up/down need not start screen from the middle ↵ | Kartik K. Agaram | 2022-05-20 | 1 | -7/+3 |
| | | | | | | | of a line But we still have work to do for cursor up/down. | ||||
| * | first stab at equally hacky cursor down support | Kartik K. Agaram | 2022-05-20 | 1 | -11/+42 |
| | | |||||
| * | stop recomputing Cursor_x now that we're saving it | Kartik K. Agaram | 2022-05-20 | 1 | -5/+3 |
| | | |||||
| * | clearer comments | Kartik K. Agaram | 2022-05-20 | 1 | -2/+3 |
| | | |||||
| * | some more logging | Kartik K. Agaram | 2022-05-20 | 1 | -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 wrong | Kartik K. Agaram | 2022-05-20 | 1 | -6/+30 |
| | | | | | | 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 up | Kartik K. Agaram | 2022-05-20 | 1 | -1/+9 |
| | | |||||
| * | first stab at supporting wrapping in cursor up | Kartik K. Agaram | 2022-05-20 | 1 | -13/+22 |
| | | | | | Looks pretty clean. | ||||
| * | bugfix | Kartik K. Agaram | 2022-05-20 | 1 | -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 top | Kartik K. Agaram | 2022-05-20 | 1 | -2/+6 |
| | | | | | | I'm not setting these yet. Rendering seems to be working after manually setting them. | ||||
| * | start using some globals | Kartik K. Agaram | 2022-05-20 | 1 | -5/+5 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-05-20 | 1 | -1/+1 |
| | | |||||
| * | start remembering where the cursor is drawn in px | Kartik K. Agaram | 2022-05-20 | 1 | -0/+2 |
| | | | | | We'll start using this in cursor up/down motions. | ||||
| * | extract a function | Kartik K. Agaram | 2022-05-20 | 1 | -8/+8 |
| | | |||||
| * | move | Kartik K. Agaram | 2022-05-19 | 1 | -35/+35 |
| | | |||||
| * | planning out cursor up/down over wrapped lines | Kartik K. Agaram | 2022-05-19 | 1 | -0/+2 |
| | | |||||
| * | bugfix: cursor past end of screen line | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | | |||||
| * | bugfix: text past cursor was rendered red on wrapped lines | Kartik K. Agaram | 2022-05-19 | 1 | -0/+2 |
| | | |||||
| * | bugfix: show cursor when past end of line | Kartik K. Agaram | 2022-05-19 | 1 | -0/+5 |
| | | |||||
| * | change text cursor shape | Kartik K. Agaram | 2022-05-19 | 1 | -1/+2 |
| | | |||||
| * | clicking to the right of a wrapped line | Kartik K. Agaram | 2022-05-19 | 1 | -9/+9 |
| | | |||||
| * | clicking now moves the cursor even on long, wrapped lines | Kartik K. Agaram | 2022-05-19 | 1 | -5/+50 |
| | | |||||
| * | rename | Kartik K. Agaram | 2022-05-19 | 1 | -2/+2 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-05-19 | 1 | -2/+7 |
| | | | | | | | As usual, binary search is hard to get right. This time I was never actually selecting between left and right when they were just one character apart. | ||||
| * | eliminate assumptions that line length == size in bytes | Kartik K. Agaram | 2022-05-19 | 1 | -9/+10 |
| | | |||||
| * | snapshot: wrapping long lines at word boundaries | Kartik K. Agaram | 2022-05-19 | 1 | -6/+82 |
| | | | | | | | Still not working: clicking on text to move the cursor aborts up/down motions still move by logical lines rather than screen lines | ||||
| * | a few more integer coordinates | Kartik K. Agaram | 2022-05-19 | 1 | -5/+5 |
| | | |||||
| * | drop unused arg | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | | |||||
| * | delete another arg that can be deduced | Kartik K. Agaram | 2022-05-19 | 1 | -3/+3 |
| | | |||||
| * | handle tab characters | Kartik K. Agaram | 2022-05-18 | 1 | -1/+8 |
| | | |||||
| * | bugfix: ensure Cursor_line is always on a text line | Kartik K. Agaram | 2022-05-18 | 1 | -0/+33 |
| | | | | | | | | | | | | | | | | | | | | | Manual test used here: abc ```lines {"p1":{"y":72,"x":82},"mode":"line","p2":{"y":29,"x":169}} ``` def ```lines {"p1":{"y":36,"x":56},"mode":"line","p2":{"y":59,"x":163}} ``` ```lines ``` ghi jkl Hitting page-down moves the cursor from abc to ghi. The 'ghi' line should be fully visible on screen. | ||||
| * | scroll past first page | Kartik K. Agaram | 2022-05-18 | 1 | -0/+13 |
| | | | | | | | Still some limitations. The text cursor has to be visible on screen, so if you have a long series of drawings without intervening lines of text you won't be able to scroll through them all. | ||||
| * | split mouse_pressed events between Text and Drawing | Kartik K. Agaram | 2022-05-17 | 1 | -7/+20 |
| | | |||||