| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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 |
| | | |||||
| * | more drawing tests | Kartik K. Agaram | 2022-06-14 | 2 | -1/+133 |
| | | |||||
| * | start writing some tests for drawings | Kartik K. Agaram | 2022-06-14 | 2 | -1/+33 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-14 | 1 | -2/+2 |
| | | |||||
| * | extract variables for drawing padding | Kartik K. Agaram | 2022-06-14 | 3 | -6/+10 |
| | | |||||
| * | extract variable Margin_left | Kartik K. Agaram | 2022-06-14 | 4 | -86/+81 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 |
| | | |||||
| * | stop generating invalid keychords | Kartik K. Agaram | 2022-06-14 | 1 | -0/+1 |
| | | |||||
| * | some more manual tests related to drawings | Kartik K. Agaram | 2022-06-14 | 1 | -0/+5 |
| | | | | | | In the process I notice an issue: we seem to be adding no-op undo records after every drawing operation. | ||||
| * | lots more tests | Kartik K. Agaram | 2022-06-14 | 2 | -32/+65 |
| | | | | | | | | I've been adding diligently to manual_tests but not actually _performing_ any manual tests before releases. They were just a todo list of automated tests to write, and long out of date. Now the list is up to date and much shorter. | ||||
| * | mouse buttons are integers, not strings | Kartik K. Agaram | 2022-06-14 | 5 | -45/+45 |
| | | | | | | | Not sure where that idiom comes from or why strings work in some places (auto-coercion?). I picked it up off some example apps. But https://love2d.org/wiki/love.mouse.isDown says it should be an integer. | ||||
| * | answered an open question | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 |
| | | | | | | The default font seems somehow different than the font created by newFont with just a font size. | ||||
| * | go through and fix similar issues | Kartik K. Agaram | 2022-06-14 | 2 | -6/+19 |
| | | | | | All places where string.sub was being passed a _pos variable. | ||||
| * | cleanup | Kartik K. Agaram | 2022-06-14 | 1 | -6/+0 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-06-14 | 3 | -4/+46 |
| | | | | | | | | | | | | | | | | | | | | | | | | manifestation: clicking past end of a long, wrapping line containing non-ASCII would cause the cursor to disappear rather than position past end of screen line. Hitting enter would then throw an assertion with the following stack trace: Error: text.lua:381: bad argument #2 to 'sub' (number expected, got nil) stack traceback: [love "boot.lua"]:345: in function <[love "boot.lua"]:341> [C]: in function 'sub' text.lua:381: in function 'insert_return' text.lua:179: in function 'keychord_pressed' main.lua:495: in function 'keychord_pressed' keychord.lua:10: in function <keychord.lua:5> app.lua:34: in function <app.lua:25> [C]: in function 'xpcall' cause: the click caused a call to Text.to_pos_on_line whose result was not on a UTF-8 character boundary. fix: make to_pos_on_line utf8-aware. | ||||
| * | bugfix: UTF-8 in compute_fragments | Kartik K. Agaram | 2022-06-14 | 3 | -5/+27 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-14 | 1 | -2/+2 |
| | | |||||
| * | new test | Kartik K. Agaram | 2022-06-12 | 2 | -0/+26 |
| | | | | | | For commit e4e12c77ad which fixed a regression caused by commit 24a0d162ef. | ||||