text.love - Fork of lines.love without drawings; useful starting point for further forks

	Commit message (Collapse)	Author	Age	Files	Lines
*	more carefully pass the 'key' arg around	Kartik K. Agaram	2024-02-04	1	-80/+80
\|
*	streamline button.lua	Kartik K. Agaram	2023-12-16	1	-0/+1
\|
*	fix all tests in LÖVE v12	Kartik K. Agaram	2023-10-09	1	-3/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This is all quite hacky. Many of my tests are unfortunately brittle to changes in text rendering. Fortunately there's only one test that currently requires a hacky special case (and a second test I tweaked slightly to be more robust). I can't think of a better approach. It doesn't help to standardize the font, because version changes still come with changes to text-shaping algorithms even if the font itself is unchanged. I could base all my assertions on the widths of individual characters, but that would make the tests much less readable and not express intent as clearly. So here we are, with hopefully just a few hacky special cases (there might be a few more as LÖVE v12 advances towards publication, and in further versions).
*	bugfix: clear selection when clicking above or below lines	Kartik K. Agaram	2023-09-20	1	-0/+24
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Matt Wynne pointed out that snap.love would crash when a node went off screen. While debugging it I noticed that selection1 was being set when it shouldn't be. Turns out I introduced a bug when I fixed the inscript bug back in June (commit 9656e137742). One invariant I want to preserve is: selection1 should be unset after a mouse click (press and release without intervening drag). This invariant was violated in my bugfix back in June. I was concerned only with selection back then, and I didn't realize I was breaking the mouse click case (in a fairly subtle way; you can have selection set, and when it's set identically to the cursor everything looks the same). I think there might still be an issue in snap.love after this fix. I noticed screen_bottom1.pos was nil, and as far as I recall that should never happen.
*	port inscript's bugfix to source editor	Kartik K. Agaram	2023-06-04	1	-0/+85
\|
*	bugfix: searching files containing unicode	Kartik K. Agaram	2023-05-13	1	-10/+10
\| \| \| \| \|	Before this change the cursor was moving, but not being highlighted properly when the cursor line contained unicode before the cursor.
*	switch source side to new screen-line-based render	Kartik K. Agaram	2023-04-03	1	-1/+1
\| \| \| \|	Also copy over the implementation of links from pensieve.love.
*	give a test a unique name	Kartik K. Agaram	2023-03-19	1	-3/+3
\|
*	bugfix	Kartik K. Agaram	2023-03-17	1	-0/+22
\| \| \| \|	Thanks Mikoláš Štrajt.
*	bugfix: up arrow when line above is a drawing	Kartik K. Agaram	2023-01-31	1	-0/+50
\| \| \| \|	This bug was introduced in commit 528c64d690 on 2022-09-05 :/
*	deduce test names on failures	Kartik K. Agaram	2023-01-20	1	-522/+428
\|
*	overzealous search-and-replace	Kartik K. Agaram	2022-12-23	1	-1/+1
\|
*	make love event names consistent	Kartik K. Agaram	2022-12-23	1	-22/+22
\| \| \| \| \|	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.
*	streamline one more test name	Kartik K. Agaram	2022-12-13	1	-14/+14
\|
*	repeat changes on source editor	Kartik K. Agaram	2022-12-13	1	-53/+36
\|
*	support selections in the source editor	Kartik K. Agaram	2022-09-06	1	-2/+408
\| \| \| \| \|	I've only tested side A so far, and included a statement of how I want side B to behave.
*	support drawings in the source editor	Kartik K. Agaram	2022-09-05	1	-1/+59
\|
*	editing source code from within the app	Kartik K. Agaram	2022-09-03	1	-0/+1609
	integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243