about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* couple of accidental globalsKartik K. Agaram2022-08-181-2/+2
| | | | Luckily they didn't bite me yet.
* get rid of some ridiculous codeKartik K. Agaram2022-08-181-15/+5
| | | | | | I guess I wrote it before I settled into the idiom of: * first change cursor * then scroll if necessary
* spurious argsKartik K. Agaram2022-08-181-18/+18
|
* dead codeKartik K. Agaram2022-08-181-2/+0
|
* generalize a functionKartik K. Agaram2022-08-183-12/+13
|
* drop some obsolete argsKartik K. Agaram2022-08-181-2/+2
|
* subsection headings in a long switchKartik K. Agaram2022-08-181-0/+2
|
* extract a variableKartik K. Agaram2022-08-181-2/+3
|
* simplifyKartik K. Agaram2022-08-181-4/+1
|
* simpler location comparisonKartik K. Agaram2022-08-171-5/+2
|
* move caching behavior inside compute_fragmentsKartik K. Agaram2022-08-171-6/+6
|
* remove some unnecessary workKartik K. Agaram2022-08-171-1/+3
|
* standardize scroll check in a few placesKartik K. Agaram2022-08-171-3/+3
| | | | | | | | | | | | I'm taking some lessons from pensieve.love here. It seem like specific pixel thresholds don't matter too much for plain lines.love. I'd probably feel safer if I just used Text.cursor_out_of_screen in these places, but it means we draw the screen twice for most events[1]. Let's see if we can get by with the current approach. [1] Or we have to start scheduling things for the next draw, which is more complex to orchestrate.
* simplify cursor-on-screen checkKartik K. Agaram2022-08-172-11/+9
|
* swap return valuesKartik K. Agaram2022-08-173-8/+8
|
* obsolete commentKartik K. Agaram2022-08-161-2/+0
|
* moveKartik K. Agaram2022-08-151-28/+28
|
* drop some unnecessary callsKartik K. Agaram2022-08-151-6/+0
|
* stop confusingly reading a globalKartik K. Agaram2022-08-151-2/+2
| | | | | | | The way Text.draw is called by edit.draw, we know it'll never be called for lines above screen_top1.line. Comparing every line on screen with screen_top1 makes no sense. The intent is really just to compare with screen_top1 only for the first line, and otherwise to ignore this check.
* new mirrorKartik K. Agaram2022-08-141-0/+1
|
* more cogent onboarding instructionsKartik K. Agaram2022-08-141-4/+7
| | | | Someone looking at the repo will probably prefer the terminal.
* remove some duplicationKartik K. Agaram2022-08-142-13/+8
|
* bugfix: obsolete location for attributeKartik K. Agaram2022-08-141-2/+2
|
* overzealous search-and-replaceKartik K. Agaram2022-08-131-1/+1
|
* bugfix: check after cursor on same line when searching upwardsKartik K. Agaram2022-08-112-1/+28
|
* search: transparently handle drawings everywhereKartik K. Agaram2022-08-111-22/+18
|
* bugfix: search upwardsKartik K. Agaram2022-08-112-1/+20
|
* bugfix: check before cursor on same lineKartik K. Agaram2022-08-112-1/+31
|
* bugfix: handle drawings when updating screen topKartik K. Agaram2022-08-111-0/+1
|
* renameKartik K. Agaram2022-08-111-24/+24
|
* bugfix: pagedown was sometimes bouncing upKartik K. Agaram2022-08-102-1/+18
|
* bugfix: backspace from start of final lineKartik K. Agaram2022-08-102-1/+21
|
* unnecessary argsKartik K. Agaram2022-08-101-1/+1
|
* hardcode some assumptions about how this app uses loveKartik K. Agaram2022-08-061-18/+11
|
* bugfix: imprecision in drawingKartik K. Agaram2022-08-032-0/+4
| | | | | | | | | | | 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.
* round one coordinateKartik K. Agaram2022-07-301-1/+1
|
* round coordinates to integers in a few placesKartik K. Agaram2022-07-291-7/+11
| | | | | | | | | | | | | Thanks Lion Kimbro for pointing out this issue. I still have to use floats for start/end angles of arcs. That might be a sign that I don't have the right serialization yet for them. Or that that feature needs to go. I started out with a hazy idea of only using 8-bit ints for coordinates, but now I'm not sure how committed I am to that constraint. While the width is always 256 units, it might be nice to create long portrait drawings at some point, whose height is greater than 256 units.
* click to the left of a lineKartik K. Agaram2022-07-294-4/+28
|
* copying to clipboard can never scrollKartik K. Agaram2022-07-271-1/+0
|
* line.y -> line_cache.starty in a few more placesKartik K. Agaram2022-07-273-14/+14
| | | | | | Disquieting that none of my tests caught these. On the other hand, I also haven't noticed any issues in practice. Perhaps cache invalidation is often unnecessary.
* have file API operate on state objectKartik K. Agaram2022-07-254-21/+20
|
* update cursor in search boxKartik K. Agaram2022-07-251-3/+1
|
* bugfix: alt-tab shouldn't emit keypress eventsKartik K. Agaram2022-07-251-1/+20
| | | | | Looks like this only happens on Linux: https://love2d.org/forums/viewtopic.php?p=249700
* moveKartik K. Agaram2022-07-251-2/+3
|
* simplify hysteresis logicKartik K. Agaram2022-07-251-8/+3
|
* bugfix: skip over drawings when searchingKartik K. Agaram2022-07-252-15/+17
|
* extract methodKartik K. Agaram2022-07-232-14/+13
|
* bugfix: online helpKartik K. Agaram2022-07-222-8/+12
| | | | Broken in the commit before last.
* bugfix: searchKartik K. Agaram2022-07-212-1/+34
| | | | | Broken since commit 188bbc73 9 days ago :/ At least we have a test for it now.
* move drawing.starty into line cacheKartik K. Agaram2022-07-203-60/+71
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-16 03:11:18 +0000