Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | snapshot - no, that's all wrong | Kartik K. Agaram | 2022-05-20 | 3 | -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 up | Kartik K. Agaram | 2022-05-20 | 2 | -1/+10 |
| | |||||
* | first stab at supporting wrapping in cursor up | Kartik K. Agaram | 2022-05-20 | 2 | -13/+33 |
| | | | | 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 | 2 | -2/+9 |
| | | | | | 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 | 2 | -6/+6 |
| | |||||
* | move | Kartik K. Agaram | 2022-05-20 | 1 | -2/+4 |
| | |||||
* | 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 | 2 | -0/+4 |
| | | | | We'll start using this in cursor up/down motions. | ||||
* | extract a function | Kartik K. Agaram | 2022-05-20 | 2 | -12/+9 |
| | |||||
* | move | Kartik K. Agaram | 2022-05-19 | 1 | -35/+35 |
| | |||||
* | planning out cursor up/down over wrapped lines | Kartik K. Agaram | 2022-05-19 | 2 | -3/+5 |
| | |||||
* | 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 | 2 | -0/+3 |
| | |||||
* | bugfix: show cursor when past end of line | Kartik K. Agaram | 2022-05-19 | 2 | -0/+6 |
| | |||||
* | change text cursor shape | Kartik K. Agaram | 2022-05-19 | 2 | -3/+5 |
| | |||||
* | clicking to the right of a wrapped line | Kartik K. Agaram | 2022-05-19 | 2 | -9/+11 |
| | |||||
* | clicking now moves the cursor even on long, wrapped lines | Kartik K. Agaram | 2022-05-19 | 2 | -7/+52 |
| | |||||
* | rename | Kartik K. Agaram | 2022-05-19 | 1 | -2/+2 |
| | |||||
* | make text and drawings the same width | Kartik K. Agaram | 2022-05-19 | 2 | -18/+18 |
| | |||||
* | comment | Kartik K. Agaram | 2022-05-19 | 1 | -6/+1 |
| | |||||
* | bugfix | Kartik K. Agaram | 2022-05-19 | 2 | -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 bytes | Kartik K. Agaram | 2022-05-19 | 2 | -12/+13 |
| | |||||
* | snapshot: wrapping long lines at word boundaries | Kartik K. Agaram | 2022-05-19 | 2 | -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 coordinates | Kartik K. Agaram | 2022-05-19 | 3 | -39/+39 |
| | |||||
* | this is a bit clearer | Kartik K. Agaram | 2022-05-19 | 1 | -2/+2 |
| | |||||
* | drop unused arg | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | |||||
* | redo y computations | Kartik K. Agaram | 2022-05-19 | 1 | -4/+8 |
| | |||||
* | simpler | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | |||||
* | another integer coordinate | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | |||||
* | delete another arg that can be deduced | Kartik K. Agaram | 2022-05-19 | 2 | -4/+4 |
| | |||||
* | delete unused arg | Kartik K. Agaram | 2022-05-19 | 2 | -2/+2 |
| | |||||
* | ensure integer coordinates | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | | | | | https://love2d.org/wiki/Text says text can appear blurry otherwise. I can't tell yet, though. | ||||
* | 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 | 3 | -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 file | Kartik K. Agaram | 2022-05-18 | 1 | -0/+2 |
| | |||||
* | scroll past first page | Kartik K. Agaram | 2022-05-18 | 3 | -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 shapes | Kartik K. Agaram | 2022-05-18 | 4 | -7/+215 |
| | |||||
* | lighter color for in-progress strokes | Kartik K. Agaram | 2022-05-18 | 1 | -0/+1 |
| | |||||
* | use the provided args everywhere | Kartik K. Agaram | 2022-05-18 | 1 | -4/+4 |
| | | | | This will be important when we implement scrolling.. | ||||
* | casting about for more helpers to extract.. | Kartik K. Agaram | 2022-05-18 | 1 | -3/+3 |
| | |||||
* | move | Kartik K. Agaram | 2022-05-18 | 1 | -91/+92 |
| | |||||
* | highlight another global | Kartik K. Agaram | 2022-05-17 | 2 | -4/+4 |
| | |||||
* | forgot to move this special case out | Kartik K. Agaram | 2022-05-17 | 2 | -3/+5 |
| | |||||
* | . | Kartik K. Agaram | 2022-05-17 | 2 | -4/+6 |
| | |||||
* | delegate update events to drawings | Kartik K. Agaram | 2022-05-17 | 2 | -21/+26 |
| | |||||
* | DRY some code | Kartik K. Agaram | 2022-05-17 | 2 | -22/+18 |
| | |||||
* | move mouse_released events to Drawing | Kartik K. Agaram | 2022-05-17 | 2 | -57/+61 |
| | |||||
* | split mouse_pressed events between Text and Drawing | Kartik K. Agaram | 2022-05-17 | 3 | -27/+44 |
| | |||||
* | split keyboard handling between Text and Drawing | Kartik K. Agaram | 2022-05-17 | 4 | -291/+302 |
| |