89b30a62ef
support mouse clicks in file navigator
2022-09-18 01:26:20 -07:00
287050d598
get rid of ugly side-effects in tests
2022-09-17 10:47:47 -07:00
fdb35ce12b
bugfix: save modified files in save directory
...
scenario: open app from .love file, press ctrl+e
Before this change the source file showed up empty.
2022-09-05 12:39:28 -07:00
e1c5a42f31
editing source code from within the app
...
integrated from pong.love via text.love:
https://merveilles.town/@akkartik/108933336531898243
2022-09-03 14:13:22 -07:00
019a829279
make App.open_for_* look more like io.open
...
Now missing files will result in similar behavior: nil file handles.
2022-08-23 13:12:24 -07:00
cfdac28e18
distinguish consistently between mouse buttons and other buttons
2022-08-23 09:36:08 -07:00
fc9490c964
reclaim a couple more functions after tests
2022-08-19 10:29:48 -07:00
6a6ff18916
hardcode some assumptions about how this app uses love
2022-08-06 09:51:32 -07:00
0ac44f0756
formatting
2022-07-16 19:27:58 -07:00
e4f9d50a55
a more radical attempt at ignoring nil y's
2022-07-13 09:31:54 -07:00
75ec5c9087
.
2022-07-12 22:13:06 -07:00
3850fbac35
make colors easier to edit
2022-07-11 23:18:26 -07:00
3be413602a
bugfix: typing should delete highlighted text
...
The test harness now also mimics real usage more precisely.
2022-06-20 10:48:35 -07:00
856c51212a
autosave slightly less aggressively
...
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
2022-06-17 15:43:31 -07:00
15acc38da9
test: autosave after any shape
2022-06-14 22:06:08 -07:00
26640c9101
new test
...
For commit e4e12c77ad24a0d162ef
2022-06-12 10:59:42 -07:00
059efba79d
override mouse state lookups in tests
...
If I'd had this stuff in my test harness earlier, two recent commits
would have failed tests and given me early warning:
ff88238ff1ff88a2a927
2022-06-12 09:04:21 -07:00
9ada7cf833
delete all tests once they've executed
2022-06-12 07:37:02 -07:00
e8ff9f285f
redundant check
2022-06-12 07:35:52 -07:00
1326914d7b
select text with shift + mouseclick
...
It's still a bit simple-minded. Most software will keep the first bound
fixed and move the second. Lines currently has the bounds in a queue of
sorts. But I have a test to indicate the behavior that is definitely
desired. We'll see if we need it to get more complex.
2022-06-04 14:54:40 -07:00
73cc12047e
select text using mouse drag
...
Doesn't yet highlight while dragging.
2022-06-03 08:11:18 -07:00
51f4f13ecc
test harness now supports copy/paste
2022-06-02 18:52:49 -07:00
a9a133e6fb
update some App framework docs
2022-05-31 17:29:58 -07:00
a603847d18
go through App in a couple more places
2022-05-29 16:37:31 -07:00
c2eee640cf
test and App helper for mouse clicks
2022-05-25 13:38:33 -07:00
442133fe7f
no, make sure to compute line width after screen dimensions
2022-05-25 13:35:32 -07:00
fa103ca2e8
couple more tests
...
Along with the App helpers needed for them.
2022-05-25 12:59:12 -07:00
a35b130f08
one bug I've repeatedly run into while testing with Moby Dick
...
https://www.hogbaysoftware.com/posts/moby-dick-workout
2022-05-23 17:39:00 -07:00
6b10c94dd5
disable all debug prints
2022-05-23 15:38:42 -07:00
c9434e4f17
snapshot
...
Why the fuck is this so fucking hard?
2022-05-23 15:22:16 -07:00
4f6a324975
bugfix: don't rely on Screen_bottom1 while scrolling
...
Setting up the test just right to test the thing I want to test was a
rube goldberg machine of constants.
2022-05-23 08:52:13 -07:00
37f1313b16
first successful pagedown test, first bug found by test
...
I also really need to rethink how people debug my programs. My approach
of inserting and deleting print() takes a lot of commitment. I need my
old trace-based whitebox testing idea. However, in my past projects I
never did figure out a good framework for tweaking how verbose a trace
to emit.
Perhaps that's too many knobs. Perhaps we just need a way to run a
single test with the most verbose trace possible. Then it's just a
matter of having the trace tell a coherent story? But even if the trace
stays out of program output in that situation, it's still in the
programmer's face in the _code_. Ugh.
Current plan: ship program with maximum tests and zero commented-out
prints. If you want to debug, insert prints. This is better than
previous, text-mode, projects just by virtue of the stdout channel being
dedicated to debug stuff.
2022-05-23 08:17:40 -07:00
5d0e0f70c4
one more implication
2022-05-22 18:32:08 -07:00
f421e1daa5
basic test-enabled framework
...
Tests still have a lot of side-effects on the real screen. We'll
gradually clean those up.
2022-05-22 18:29:52 -07:00
555726a87d
rename
2022-05-22 18:23:04 -07:00
Kartik K. Agaram