| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | bugfix: naming points | Kartik K. Agaram | 2023-03-26 | 1 | -0/+35 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2023-03-26 | 1 | -0/+31 |
| | | |||||
| * | deduce test names on failures | Kartik K. Agaram | 2023-01-20 | 1 | -259/+237 |
| | | |||||
| * | make love event names consistent | Kartik K. Agaram | 2022-12-23 | 1 | -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_pressed | Kartik K. Agaram | 2022-12-12 | 1 | -1/+1 |
| | | | | | I don't understand why, but we need to fix production. | ||||
| * | switch a bunch of tests to textinput events | Kartik K. Agaram | 2022-12-12 | 1 | -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-stroke | Kartik K. Agaram | 2022-12-12 | 1 | -1/+1 |
| | | |||||
| * | stop tracking wallclock time | Kartik K. Agaram | 2022-11-03 | 1 | -9/+9 |
| | | | | | We only need time differences. | ||||
| * | have file API operate on state object | Kartik K. Agaram | 2022-07-25 | 1 | -8/+8 |
| | | |||||
| * | move drawing.starty into line cache | Kartik K. Agaram | 2022-07-20 | 1 | -10/+10 |
| | | |||||
| * | clean up a cross-test leakage | Kartik K. Agaram | 2022-07-19 | 1 | -9/+9 |
| | | |||||
| * | separate data structure for each line's cache data | Kartik K. Agaram | 2022-07-17 | 1 | -0/+30 |
| | | | | | I have no idea what the performance implications of this are.. | ||||
| * | bring back a set of constants | Kartik K. Agaram | 2022-07-16 | 1 | -79/+79 |
| | | | | | | It's starting to sink in that I don't want hard-coded constants inside objects. | ||||
| * | more decoupling editor tests from App | Kartik K. Agaram | 2022-07-16 | 1 | -13/+13 |
| | | |||||
| * | make test initializations a little more obvious | Kartik K. Agaram | 2022-07-15 | 1 | -43/+43 |
| | | |||||
| * | a bug I've never run into | Kartik K. Agaram | 2022-07-13 | 1 | -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 coordinates | Kartik K. Agaram | 2022-07-12 | 1 | -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 tests | Kartik K. Agaram | 2022-07-12 | 1 | -87/+87 |
| | | |||||
| * | start passing in Editor_state explicitly | Kartik K. Agaram | 2022-07-12 | 1 | -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 globals | Kartik K. Agaram | 2022-07-12 | 1 | -248/+248 |
| | | | | | We're still accessing them through a global. But we'll change that next. | ||||
| * | start decoupling editor tests from App | Kartik K. Agaram | 2022-07-11 | 1 | -24/+24 |
| | | |||||
| * | bugfix: 'escape' to cancel a stroke | Kartik K. Agaram | 2022-07-05 | 1 | -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 margin | Kartik K. Agaram | 2022-06-30 | 1 | -20/+20 |
| | | |||||
| * | rip out notion of Line_width | Kartik K. Agaram | 2022-06-30 | 1 | -40/+20 |
| | | |||||
| * | keep drawings within the line width slider as well | Kartik K. Agaram | 2022-06-22 | 1 | -20/+20 |
| | | |||||
| * | correct commit f3abc2cbf2 | Kartik K. Agaram | 2022-06-17 | 1 | -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 aggressively | Kartik K. Agaram | 2022-06-17 | 1 | -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 arcs | Kartik K. Agaram | 2022-06-15 | 1 | -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. Agaram | 2022-06-14 | 1 | -2/+36 |
| | | |||||
| * | test: undo moving point | Kartik K. Agaram | 2022-06-14 | 1 | -0/+47 |
| | | |||||
| * | test: undo naming a point | Kartik K. Agaram | 2022-06-14 | 1 | -0/+43 |
| | | | | | Also ensure we autosave. | ||||
| * | test: autosave after name/move/delete of point | Kartik K. Agaram | 2022-06-14 | 1 | -0/+22 |
| | | |||||
| * | test: autosave after any shape | Kartik K. Agaram | 2022-06-14 | 1 | -0/+26 |
| | | |||||
| * | tests: deleting points/shapes | Kartik K. Agaram | 2022-06-14 | 1 | -1/+105 |
| | | |||||
| * | test: moving a point | Kartik K. Agaram | 2022-06-14 | 1 | -0/+40 |
| | | | | | | 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 | -0/+35 |
| | | |||||
| * | tests for drawing polygons | Kartik K. Agaram | 2022-06-14 | 1 | -10/+171 |
| | | |||||
| * | more drawing tests | Kartik K. Agaram | 2022-06-14 | 1 | -0/+132 |
| | | |||||
| * | start writing some tests for drawings | Kartik K. Agaram | 2022-06-14 | 1 | -0/+30 |