about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* bugfix: cursor past end of screen lineKartik K. Agaram2022-05-191-1/+1
|
* bugfix: text past cursor was rendered red on wrapped linesKartik K. Agaram2022-05-192-0/+3
|
* bugfix: show cursor when past end of lineKartik K. Agaram2022-05-192-0/+6
|
* change text cursor shapeKartik K. Agaram2022-05-192-3/+5
|
* clicking to the right of a wrapped lineKartik K. Agaram2022-05-192-9/+11
|
* clicking now moves the cursor even on long, wrapped linesKartik K. Agaram2022-05-192-7/+52
|
* renameKartik K. Agaram2022-05-191-2/+2
|
* make text and drawings the same widthKartik K. Agaram2022-05-192-18/+18
|
* commentKartik K. Agaram2022-05-191-6/+1
|
* bugfixKartik K. Agaram2022-05-192-2/+8
| | | | | | 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 bytesKartik K. Agaram2022-05-192-12/+13
|
* snapshot: wrapping long lines at word boundariesKartik K. Agaram2022-05-192-7/+85
| | | | | | 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 coordinatesKartik K. Agaram2022-05-193-39/+39
|
* this is a bit clearerKartik K. Agaram2022-05-191-2/+2
|
* drop unused argKartik K. Agaram2022-05-191-1/+1
|
* redo y computationsKartik K. Agaram2022-05-191-4/+8
|
* simplerKartik K. Agaram2022-05-191-1/+1
|
* another integer coordinateKartik K. Agaram2022-05-191-1/+1
|
* delete another arg that can be deducedKartik K. Agaram2022-05-192-4/+4
|
* delete unused argKartik K. Agaram2022-05-192-2/+2
|
* ensure integer coordinatesKartik K. Agaram2022-05-191-1/+1
| | | | | https://love2d.org/wiki/Text says text can appear blurry otherwise. I can't tell yet, though.
* handle tab charactersKartik K. Agaram2022-05-181-1/+8
|
* bugfix: ensure Cursor_line is always on a text lineKartik K. Agaram2022-05-183-3/+45
| | | | | | | | | | | | | | | | | | | | 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.
* bugfix: position cursor up top when loading fileKartik K. Agaram2022-05-181-0/+2
|
* scroll past first pageKartik K. Agaram2022-05-183-20/+63
| | | | | | 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.
* rectangle and square shapesKartik K. Agaram2022-05-184-7/+215
|
* lighter color for in-progress strokesKartik K. Agaram2022-05-181-0/+1
|
* use the provided args everywhereKartik K. Agaram2022-05-181-4/+4
| | | | This will be important when we implement scrolling..
* casting about for more helpers to extract..Kartik K. Agaram2022-05-181-3/+3
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-28 11:13:43 +0000