about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
| | * speculatively recommend new LÖVE v11.5 in all forksKartik K. Agaram2023-12-031-1/+1
| | |
| | * bugfix: version checkKartik K. Agaram2023-12-033-2/+6
| | |
* | | Merge text.loveKartik K. Agaram2023-12-031-5/+0
|\| |
| * | Merge lines.loveKartik K. Agaram2023-12-032-10/+0
| |\|
| | * clearing starty is redundant in mutationsKartik K. Agaram2023-12-032-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | We'll end up calling Text.redraw_all anyway, which will clear starty and much more besides. We'll still conservatively continue clearing starty in a few places where there's a possibility that Text.redraw_all may not be called. This change is riskier than most.
* | | Merge text.loveKartik K. Agaram2023-12-012-1/+3
|\| |
| * | Merge lines.loveKartik K. Agaram2023-12-012-1/+3
| |\|
| | * mouse button state in source editorKartik K. Agaram2023-12-012-1/+3
| | |
* | | Merge text.loveKartik K. Agaram2023-12-012-1/+3
|\| |
| * | Merge lines.loveKartik K. Agaram2023-12-012-1/+3
| |\|
| | * manually maintain mouse button press stateKartik K. Agaram2023-12-012-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just checking mouse.isDown works if the editor is the entirety of the app, as is true in this fork. However, we often want to introduce other widgets. We'd like tapping on them to not cause the selection to flash: https://news.ycombinator.com/context?id=38404923&submission=38397715 The right architecture to enforce this is: have each layer of the UI maintain its own state machine between mouse_press and mouse_release events. And only check the state machine in the next level down rather than lower layers or the bottommost layer of raw LÖVE.
* | | Merge text.loveKartik K. Agaram2023-11-251-1/+8
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-251-1/+8
| |\|
| | * port keyboard layout handling to source editorKartik K. Agaram2023-11-251-1/+8
| | |
* | | Merge text.loveKartik K. Agaram2023-11-251-0/+13
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-251-1/+8
| |\|
| | * improved handling of other keyboard layoutsKartik K. Agaram2023-11-251-1/+8
| | |
* | | Merge text.loveKartik K. Agaram2023-11-242-2/+18
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-242-2/+18
| |\|
| | * bugfix: infinite loop inside a very narrow windowKartik K. Agaram2023-11-242-2/+6
| | | | | | | | | | | | | | | | | | I'm not sure this can trigger everywhere (I've only been able to exercise it in Lua Carousel), but it seems like a safety net worth having against future modifications by anybody.
| | * establish a fairly fundamental invariantKartik K. Agaram2023-11-242-0/+12
| | | | | | | | | | | | | | | | | | | | | This commit doesn't guarantee we'll always catch it. But if this invariant is violated, things can get quite difficult to debug. I found in the Lua Carousel fork that all the xpcalls I keep around were actively hindering my ability to notice this invariant being violated.
* | | Merge text.loveKartik K. Agaram2023-11-181-1/+2
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-181-1/+2
| |\|
| | * late-bind my App.* handlersKartik K. Agaram2023-11-181-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | This came up when trying to integrate my apps with the vudu debugger (https://github.com/deltadaedalus/vudu). In general, it's a subtle part of LÖVE's semantics that you can modify event handlers any time and your modifications will get picked up. Now my Freewheeling Apps will follow this norm as well.
* | | Merge text.loveKartik K. Agaram2023-11-1813-104/+76
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-1814-112/+84
| |\|
| | * audit all assertsKartik K. Agaram2023-11-1815-132/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each one should provide a message that will show up within LÖVE. Stop relying on nearby prints to the terminal. I also found some unnecessary ones. There is some potential here for performance regressions: the format() calls will trigger whether or not the assertion fails, and cause allocations. So far Lua's GC seems good enough to manage the load even with Moby Dick, even in some situations that caused issues in the past like undo.
* | | Merge text.loveKartik K. Agaram2023-11-121-5/+13
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-121-5/+13
| |\|
| | * remove some dead codeKartik K. Agaram2023-11-121-1/+0
| | | | | | | | | | | | We have an early exit for 'error' mode in this function.
| | * check for 'error' mode in a few more placesKartik K. Agaram2023-11-121-5/+14
| | | | | | | | | | | | | | | | | | | | | In particular, I want to be able to switch to 'error' mode rather than throw a real error() on test failures, because that's a little more responsive and might be recoverable. (On some Android devices the font is slightly different, and tests fail as a result.)
* | | Merge text.loveKartik K. Agaram2023-11-101-3/+2
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-101-3/+2
| |\|
| | * improve a nameKartik K. Agaram2023-11-101-2/+2
| | |
| | * clean up a debug printKartik K. Agaram2023-11-101-1/+0
| | |
* | | Merge text.loveKartik K. Agaram2023-11-101-1/+22
|\| |
| * | Merge lines.loveKartik K. Agaram2023-11-101-1/+22
| |\|
| | * clean up some cruft from error callstacksKartik K. Agaram2023-11-101-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | before: stack traceback: [string "text.lua"]:9: in function 'draw' [string "edit.lua"]:200: in function 'draw' [string "run.lua"]:140: in function 'draw' [string "main.lua"]:162: in function <[string "main.lua"]:155> [C]: in function 'xpcall' [string "app.lua"]:38: in function <[string "app.lua"]:20> [C]: in function 'xpcall' [love "boot.lua"]:370: in function <[love "boot.lua"]:337> after: stack traceback: text.lua:9: in function 'draw' edit.lua:200: in function 'draw' run.lua:140: in function 'draw' main.lua:162: in function <[string "main.lua"]:155> [C]: in function 'xpcall' app.lua:38: in function <[string "app.lua"]:20> [C]: in function 'xpcall' [love "boot.lua"]:370: in function <[love "boot.lua"]:337>
| | * remove a no-op regex munging on callstacksKartik K. Agaram2023-11-101-1/+1
| | | | | | | | | | | | Port of a fix "upstream": commit b38f172ceb in template-live-editor.
* | | Merge text.loveKartik K. Agaram2023-10-285-9/+13
|\| |
| * | Merge lines.loveKartik K. Agaram2023-10-285-9/+13
| |\|
| | * use my name for a dirKartik K. Agaram2023-10-272-2/+2
| | |
| | * remove stale variable from docsKartik K. Agaram2023-10-271-1/+1
| | |
| | * change section delimiters in log for OpenBSDKartik K. Agaram2023-10-202-6/+10
| | | | | | | | | | | | Thanks eril for the report and patch.
* | | Merge text.loveKartik K. Agaram2023-10-165-8/+4
|\| |
| * | Merge lines.loveKartik K. Agaram2023-10-165-8/+4
| |\|
| | * use color alpha in button backgroundsKartik K. Agaram2023-10-161-1/+1
| | |
| | * clearer API for drawing a buttonKartik K. Agaram2023-10-166-9/+5
| | | | | | | | | | | | | | | | | | Make it more obvious that the color passed in is just for the background. The icon will do the rest. r/g/b keys are more consistent with App.color().
* | | Merge text.loveKartik K. Agaram2023-10-151-0/+9
|\| |
| * | Merge lines.loveKartik K. Agaram2023-10-151-0/+9
| |\|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-07-19 03:15:44 +0000