about summary refs log tree commit diff stats
path: root/drawing_tests.lua
Commit message (Collapse)AuthorAgeFilesLines
* deduce test names on failuresKartik K. Agaram2023-01-201-259/+237
|
* make love event names consistentKartik K. Agaram2022-12-231-21/+21
| | | | | I want the words to be easy to read, and to use a consistent tense. update and focus seem more timeless; let's make everything like those.
* switch one call back to keychord_pressedKartik K. Agaram2022-12-121-1/+1
| | | | I don't understand why, but we need to fix production.
* switch a bunch of tests to textinput eventsKartik K. Agaram2022-12-121-18/+18
| | | | | textinput is strictly more realistic than keychord_pressed, which doesn't cause any textinput events. Use it wherever possible.
* bugfix in changing shape mid-strokeKartik K. Agaram2022-12-121-1/+1
|
* stop tracking wallclock timeKartik K. Agaram2022-11-031-9/+9
| | | | We only need time differences.
* have file API operate on state objectKartik K. Agaram2022-07-251-8/+8
|
* move drawing.starty into line cacheKartik K. Agaram2022-07-201-10/+10
|
* clean up a cross-test leakageKartik K. Agaram2022-07-191-9/+9
|
* separate data structure for each line's cache dataKartik K. Agaram2022-07-171-0/+30
| | | | I have no idea what the performance implications of this are..
* bring back a set of constantsKartik K. Agaram2022-07-161-79/+79
| | | | | It's starting to sink in that I don't want hard-coded constants inside objects.
* more decoupling editor tests from AppKartik K. Agaram2022-07-161-13/+13
|
* make test initializations a little more obviousKartik K. Agaram2022-07-151-43/+43
|
* a bug I've never run intoKartik K. Agaram2022-07-131-0/+2
| | | | | | The previous commit was failing inside a test that I can't reproduce manually. Perhaps it's something about how often draw/update run in practice. Anyways, it's definitely uncovered a real issue.
* left/right margin -> left/right coordinatesKartik K. Agaram2022-07-121-101/+123
| | | | | Editor state initialization now depends on window dimensions, so we have to more carefully orchestrate startup.
* call edit rather than App callbacks in testsKartik K. Agaram2022-07-121-87/+87
|
* start passing in Editor_state explicitlyKartik K. Agaram2022-07-121-24/+24
| | | | | | | | | | | | In this commit, top-level edit functions: - edit.draw - edit.update - edit.quit - edit.mouse_pressed - edit.mouse_released - edit.textinput - edit.keychord_pressed - edit.key_released
* group all editor globalsKartik K. Agaram2022-07-121-248/+248
| | | | We're still accessing them through a global. But we'll change that next.
* start decoupling editor tests from AppKartik K. Agaram2022-07-111-24/+24
|
* bugfix: 'escape' to cancel a strokeKartik K. Agaram2022-07-051-0/+22
| | | | | | This has been broken since commit b544e8c357 on May 17 :/ I'm just undoing that commit, which turns out to be completely unnecessary. And adding a test.
* right marginKartik K. Agaram2022-06-301-20/+20
|
* rip out notion of Line_widthKartik K. Agaram2022-06-301-40/+20
|
* keep drawings within the line width slider as wellKartik K. Agaram2022-06-221-20/+20
|
* correct commit f3abc2cbf2Kartik K. Agaram2022-06-171-1/+26
| | | | | | I can't be trusted to do anything without a test. This should fix #5. Please reopen if it doesn't.
* autosave slightly less aggressivelyKartik K. Agaram2022-06-171-0/+30
| | | | | | | | 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
* stop recording points for arcsKartik K. Agaram2022-06-151-1/+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.
* all pending manual tests done!Kartik K. Agaram2022-06-141-2/+36
|
* test: undo moving pointKartik K. Agaram2022-06-141-0/+47
|
* test: undo naming a pointKartik K. Agaram2022-06-141-0/+43
| | | | Also ensure we autosave.
* test: autosave after name/move/delete of pointKartik K. Agaram2022-06-141-0/+22
|
* test: autosave after any shapeKartik K. Agaram2022-06-141-0/+26
|
* tests: deleting points/shapesKartik K. Agaram2022-06-141-1/+105
|
* test: moving a pointKartik K. Agaram2022-06-141-0/+40
| | | | | I found some code in the process that seems unreachable. Some chance of a regression here..
* test: naming a pointKartik K. Agaram2022-06-141-0/+35
|
* tests for drawing polygonsKartik K. Agaram2022-06-141-10/+171
|
* more drawing testsKartik K. Agaram2022-06-141-0/+132
|
* start writing some tests for drawingsKartik K. Agaram2022-06-141-0/+30