| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | better fix for commit 3ffc2ed8f | Kartik K. Agaram | 2022-06-20 | 1 | -0/+1 | |
| | | | | | | | | | | I'm giving up finding a more generalized solution. The issue is that we need the correct selection state right up to the point where we modify Lines, in order to capture precise undo state. Hopefully there aren't any other keychords that should clear the selection. | |||||
| * | revert selection logic to before commit 3ffc2ed8f | Kartik K. Agaram | 2022-06-20 | 3 | -8/+12 | |
| | | | | | | We still have a failing test, but now it's the one we introduced in commit 3ffc2ed8f. | |||||
| * | snapshot: test for a new regression | Kartik K. Agaram | 2022-06-20 | 1 | -0/+22 | |
| | | | | | | | Caused by commit 3ffc2ed8f. We might need to bring back a lot of complexity for this. | |||||
| * | selection bugfix | Kartik K. Agaram | 2022-06-20 | 2 | -1/+19 | |
| | | ||||||
| * | much simpler | Kartik K. Agaram | 2022-06-20 | 2 | -31/+8 | |
| | | | | | | | | | We just need to ensure textinput events never make use of selection state. All tests are passing, but I'm aware of a couple of issues. But now we can keep all the special cases in one place. | |||||
| * | some early returns should be asserts | Kartik K. Agaram | 2022-06-20 | 1 | -1/+3 | |
| | | ||||||
| * | move Selection1 clearing past business logic | Kartik K. Agaram | 2022-06-20 | 1 | -10/+10 | |
| | | | | | | | Now all the cases that clear Selection1 do so in a very consistent way at the end of each case. And cases that set Selection1 symmetrically do so at the start of each case. | |||||
| * | remove some redundant checks | Kartik K. Agaram | 2022-06-20 | 1 | -30/+10 | |
| | | | | | Now all the cases manage Selection1 similarly. | |||||
| * | no, that's not right | Kartik K. Agaram | 2022-06-20 | 3 | -3/+40 | |
| | | | | | | | | | | | | | | | Bugfix: we want selections to persist even when we lift up the shift key. This requires hoisting some code inside every case inside the whole keypress hierarchy, to ensure we never clear selections before textinput events can handle them. Current cross-cutting concerns we're explicitly scattering code for. - autosave - undo - selection management | |||||
| * | bugfix: typing should delete highlighted text | Kartik K. Agaram | 2022-06-20 | 3 | -9/+29 | |
| | | | | | The test harness now also mimics real usage more precisely. | |||||
| * | clearer copy | Kartik K. Agaram | 2022-06-20 | 1 | -2/+3 | |
| | | ||||||
| * | bugfix | Kartik K. Agaram | 2022-06-19 | 3 | -1/+27 | |
| | | | | | | | | | | | | | | | | To reproduce: click to position cursor at end of a line hit enter press any key before: newline got erased and key got added to previous line now: newline is preserved The new test checks a generalization of this. | |||||
| * | bugfix: crash in Text.up() after return | Kartik K. Agaram | 2022-06-19 | 3 | -38/+31 | |
| | | | | | Let's just make all the utf8.offset calculations more defensive. | |||||
| * | typos | Kartik K. Agaram | 2022-06-19 | 1 | -2/+2 | |
| | | ||||||
| * | fix help for rectangles and squares | Kartik K. Agaram | 2022-06-18 | 1 | -0/+20 | |
| | | | | | Thanks John Blommers (https://github.com/akkartik/lines.love/issues/1#issuecomment-1159582457) | |||||
| * | make sure to save right when quitting | Kartik K. Agaram | 2022-06-18 | 1 | -0/+5 | |
| | | | | | I just noticed a few characters missing from one of my notes. | |||||
| * | correct location of the line width slider | Kartik K. Agaram | 2022-06-18 | 3 | -4/+5 | |
| | | ||||||
| * | clean up | Kartik K. Agaram | 2022-06-17 | 3 | -30/+0 | |
| | | ||||||
| * | more precise shape selection | Kartik K. Agaram | 2022-06-17 | 2 | -7/+35 | |
| | | | | | | | | It's important that the error be additive rather than multiplicative, otherwise the area grows asymmetrically along a line. Hopefully freehand drawings will work more intuitively now. | |||||
| * | correct commit f3abc2cbf2 | Kartik K. Agaram | 2022-06-17 | 3 | -10/+48 | |
| | | | | | | | I can't be trusted to do anything without a test. This should fix #5. Please reopen if it doesn't. | |||||
| * | drop last couple of manual tests | Kartik K. Agaram | 2022-06-17 | 3 | -13/+32 | |
| | | ||||||
| * | manual test for adjusting line width | Kartik K. Agaram | 2022-06-17 | 1 | -0/+6 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-17 | 1 | -1/+1 | |
| | | ||||||
| * | better handle moving points | Kartik K. Agaram | 2022-06-17 | 2 | -15/+5 | |
| | | | | | | This should hopefully address #5. I'm removing some constraints from manhattan lines, rectangles and squares. | |||||
| * | affordance to adjust width for word wrap | Kartik K. Agaram | 2022-06-17 | 2 | -1/+43 | |
| | | ||||||
| * | indent | Kartik K. Agaram | 2022-06-17 | 1 | -4/+4 | |
| | | ||||||
| * | autosave slightly less aggressively | Kartik K. Agaram | 2022-06-17 | 4 | -18/+72 | |
| | | | | | | | | | It might reduce wear and tear on disk, and losing 3 seconds of data doesn't feel catastrophic (short of a C-z rampage). Thanks to the love2d.org community for the suggestion: https://love2d.org/forums/viewtopic.php?f=14&t=93173 | |||||
| * | document one more shortcut | Kartik K. Agaram | 2022-06-17 | 1 | -0/+1 | |
| | | ||||||
| * | tweak to Readme | Kartik K. Agaram | 2022-06-15 | 1 | -2/+2 | |
| | | ||||||
| * | new fork for #1 | Kartik K. Agaram | 2022-06-15 | 1 | -0/+4 | |
| | | ||||||
| * | bugfix: alignment of help screen | Kartik K. Agaram | 2022-06-15 | 1 | -33/+33 | |
| | | ||||||
| * | dead code | Kartik K. Agaram | 2022-06-15 | 1 | -45/+0 | |
| | | ||||||
| * | move | Kartik K. Agaram | 2022-06-15 | 1 | -28/+28 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-15 | 1 | -6/+3 | |
| | | ||||||
| * | stop recording points for arcs | Kartik K. Agaram | 2022-06-15 | 2 | -2/+1 | |
| | | | | | | | It was kinda weird that we were recording the start but not the end. And moving the start point didn't actually affect the arc. Let's see if we actually ever need it. | |||||
| * | move current mode indicator slightly | Kartik K. Agaram | 2022-06-15 | 1 | -2/+2 | |
| | | ||||||
| * | standardize on ordering of cases | Kartik K. Agaram | 2022-06-15 | 1 | -9/+9 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-14 | 1 | -3/+3 | |
| | | ||||||
| * | all pending manual tests done! | Kartik K. Agaram | 2022-06-14 | 2 | -7/+39 | |
| | | ||||||
| * | test: undo moving point | Kartik K. Agaram | 2022-06-14 | 2 | -1/+47 | |
| | | ||||||
| * | test: undo naming a point | Kartik K. Agaram | 2022-06-14 | 3 | -1/+45 | |
| | | | | | Also ensure we autosave. | |||||
| * | test: autosave after name/move/delete of point | Kartik K. Agaram | 2022-06-14 | 2 | -3/+22 | |
| | | ||||||
| * | test: autosave after any shape | Kartik K. Agaram | 2022-06-14 | 4 | -4/+43 | |
| | | ||||||
| * | tests: deleting points/shapes | Kartik K. Agaram | 2022-06-14 | 1 | -1/+105 | |
| | | ||||||
| * | test: moving a point | Kartik K. Agaram | 2022-06-14 | 3 | -16/+44 | |
| | | | | | | I found some code in the process that seems unreachable. Some chance of a regression here.. | |||||
| * | test: naming a point | Kartik K. Agaram | 2022-06-14 | 3 | -2/+39 | |
| | | ||||||
| * | a little more prose describing manual_tests | Kartik K. Agaram | 2022-06-14 | 2 | -23/+30 | |
| | | ||||||
| * | one less manual test | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 | |
| | | | | | Still a few more we can write. | |||||
| * | drop non-existent feature from comment | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 | |
| | | ||||||
| * | tests for drawing polygons | Kartik K. Agaram | 2022-06-14 | 2 | -11/+180 | |
| | | ||||||