about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* clearer copyKartik K. Agaram2022-06-201-2/+3
|
* bugfixKartik K. Agaram2022-06-193-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 returnKartik K. Agaram2022-06-193-38/+31
| | | | Let's just make all the utf8.offset calculations more defensive.
* typosKartik K. Agaram2022-06-191-2/+2
|
* fix help for rectangles and squaresKartik K. Agaram2022-06-181-0/+20
| | | | Thanks John Blommers (https://github.com/akkartik/lines.love/issues/1#issuecomment-1159582457)
* make sure to save right when quittingKartik K. Agaram2022-06-181-0/+5
| | | | I just noticed a few characters missing from one of my notes.
* correct location of the line width sliderKartik K. Agaram2022-06-183-4/+5
|
* clean upKartik K. Agaram2022-06-173-30/+0
|
* more precise shape selectionKartik K. Agaram2022-06-172-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 f3abc2cbf2Kartik K. Agaram2022-06-173-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 testsKartik K. Agaram2022-06-173-13/+32
|
* manual test for adjusting line widthKartik K. Agaram2022-06-171-0/+6
|
* .Kartik K. Agaram2022-06-171-1/+1
|
* better handle moving pointsKartik K. Agaram2022-06-172-15/+5
| | | | | This should hopefully address #5. I'm removing some constraints from manhattan lines, rectangles and squares.
* affordance to adjust width for word wrapKartik K. Agaram2022-06-172-1/+43
|
* indentKartik K. Agaram2022-06-171-4/+4
|
* autosave slightly less aggressivelyKartik K. Agaram2022-06-174-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 shortcutKartik K. Agaram2022-06-171-0/+1
|
* tweak to ReadmeKartik K. Agaram2022-06-151-2/+2
|
* new fork for #1Kartik K. Agaram2022-06-151-0/+4
|
* bugfix: alignment of help screenKartik K. Agaram2022-06-151-33/+33
|
* dead codeKartik K. Agaram2022-06-151-45/+0
|
* moveKartik K. Agaram2022-06-151-28/+28
|
* .Kartik K. Agaram2022-06-151-6/+3
|
* stop recording points for arcsKartik K. Agaram2022-06-152-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 slightlyKartik K. Agaram2022-06-151-2/+2
|
* standardize on ordering of casesKartik K. Agaram2022-06-151-9/+9
|
* .Kartik K. Agaram2022-06-141-3/+3
|
* all pending manual tests done!Kartik K. Agaram2022-06-142-7/+39
|
* test: undo moving pointKartik K. Agaram2022-06-142-1/+47
|
* test: undo naming a pointKartik K. Agaram2022-06-143-1/+45
| | | | Also ensure we autosave.
* test: autosave after name/move/delete of pointKartik K. Agaram2022-06-142-3/+22
|
* test: autosave after any shapeKartik K. Agaram2022-06-144-4/+43
|
* tests: deleting points/shapesKartik K. Agaram2022-06-141-1/+105
|
* test: moving a pointKartik K. Agaram2022-06-143-16/+44
| | | | | I found some code in the process that seems unreachable. Some chance of a regression here..
* test: naming a pointKartik K. Agaram2022-06-143-2/+39
|
* a little more prose describing manual_testsKartik K. Agaram2022-06-142-23/+30
|
* one less manual testKartik K. Agaram2022-06-141-1/+0
| | | | Still a few more we can write.
* drop non-existent feature from commentKartik K. Agaram2022-06-141-1/+0
|
* tests for drawing polygonsKartik K. Agaram2022-06-142-11/+180
|
* more drawing testsKartik K. Agaram2022-06-142-1/+133
|
* start writing some tests for drawingsKartik K. Agaram2022-06-142-1/+33
|
* .Kartik K. Agaram2022-06-141-2/+2
|
* extract variables for drawing paddingKartik K. Agaram2022-06-143-6/+10
|
* extract variable Margin_leftKartik K. Agaram2022-06-144-86/+81
|
* .Kartik K. Agaram2022-06-141-1/+0
|
* stop generating invalid keychordsKartik K. Agaram2022-06-141-0/+1
|
* some more manual tests related to drawingsKartik K. Agaram2022-06-141-0/+5
| | | | | In the process I notice an issue: we seem to be adding no-op undo records after every drawing operation.
* lots more testsKartik K. Agaram2022-06-142-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 stringsKartik K. Agaram2022-06-145-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.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-04 02:11:28 +0000