| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Merge lines.love | Kartik K. Agaram | 2023-03-30 | 1 | -11/+8 |
| |\ | |||||
| | * | obsolete manual test | Kartik K. Agaram | 2023-03-30 | 1 | -4/+0 |
| | | | |||||
| | * | better formatting | Kartik K. Agaram | 2023-03-28 | 1 | -9/+11 |
| | | | |||||
| * | | Merge lines.love | Kartik K. Agaram | 2022-12-23 | 1 | -0/+3 |
| |\| | |||||
| | * | require editor margins to be ints | Kartik K. Agaram | 2022-12-23 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | | Not directly relevant here, but forks of this project that permit zooming can run into weird glitches if margins are not a whole number of pixels. I'd always assumed a type system that divided ints into floats was strictly superior, but now I have experienced a situation where requiring ints isn't just a compromise for the underlying CPU implementation. Particularly since Lua's print() silently hides really tiny fractions. | ||||
| | * | editing source code from within the app | Kartik K. Agaram | 2022-09-03 | 1 | -5/+16 |
| | | | | | | | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243 | ||||
| * | | editing source code from within the app | Kartik K. Agaram | 2022-09-03 | 1 | -5/+16 |
| |/ | | | | integrated from pong.love: https://merveilles.town/@akkartik/108933336531898243 | ||||
| * | bugfix: imprecision in drawing | Kartik K. Agaram | 2022-08-03 | 1 | -0/+1 |
| | | | | | | | | | | | | scenario: slowly press down mouse button and drag to draw a line release mouse button Before this commit the point would jump just a little bit on release, and points would go slightly to the left of where I expect. Yet another thing it's hard to write an automated test for. | ||||
| * | bugfix: where cursor is drawn | Kartik K. Agaram | 2022-07-20 | 1 | -0/+4 |
| | | | | | | | | The published version of lines.love was broken for almost an hour. The cursor would render one position to the right of where it really is. To fix it, this commit rolls back 26ba6e4e5a71. There doesn't seem a good way to test it. | ||||
| * | reorg manual tests doc | Kartik K. Agaram | 2022-07-20 | 1 | -9/+7 |
| | | |||||
| * | experiment: new edit namespace | Kartik K. Agaram | 2022-07-11 | 1 | -0/+4 |
| | | | | | | | | | Still lots to do, but the eventual hope is that this will make this project's code easier to reuse from other LÖVE projects. One gotcha: even as we start putting code more aggressively into nested tables, tests must remain at the top-level. Otherwise they won't run. | ||||
| * | ugh, handle absolute as well as relative paths | Kartik K. Agaram | 2022-07-01 | 1 | -0/+8 |
| | | |||||
| * | bugfix: manage screen_top and cursor when resizing | Kartik K. Agaram | 2022-07-01 | 1 | -0/+3 |
| | | |||||
| * | record one more case I can't automatically detect | Kartik K. Agaram | 2022-06-23 | 1 | -0/+5 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-06-21 | 1 | -0/+4 |
| | | | | | | State changes when inserting return are now in sync with other characters. | ||||
| * | clearer copy | Kartik K. Agaram | 2022-06-20 | 1 | -2/+3 |
| | | |||||
| * | drop last couple of manual tests | Kartik K. Agaram | 2022-06-17 | 1 | -12/+0 |
| | | |||||
| * | manual test for adjusting line width | Kartik K. Agaram | 2022-06-17 | 1 | -0/+6 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-17 | 1 | -1/+1 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-14 | 1 | -3/+3 |
| | | |||||
| * | all pending manual tests done! | Kartik K. Agaram | 2022-06-14 | 1 | -5/+3 |
| | | |||||
| * | test: undo moving point | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 |
| | | |||||
| * | test: undo naming a point | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 |
| | | | | | Also ensure we autosave. | ||||
| * | test: autosave after name/move/delete of point | Kartik K. Agaram | 2022-06-14 | 1 | -3/+0 |
| | | |||||
| * | test: autosave after any shape | Kartik K. Agaram | 2022-06-14 | 1 | -1/+0 |
| | | |||||
| * | test: moving a point | Kartik K. Agaram | 2022-06-14 | 1 | -3/+0 |
| | | | | | | 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 | 1 | -1/+0 |
| | | |||||
| * | a little more prose describing manual_tests | Kartik K. Agaram | 2022-06-14 | 1 | -0/+30 |