about summary refs log tree commit diff stats
path: root/run.lua
Commit message (Collapse)AuthorAgeFilesLines
* drop an unused argKartik K. Agaram2023-07-111-2/+2
|
* standardize between run and source some moreKartik K. Agaram2023-07-101-3/+1
| | | | | We shouldn't be thinking about saving settings when we're initializing window geometry.
* simplify saving settingsKartik K. Agaram2023-07-101-3/+1
| | | | We don't ever call one app's settings while Current_app is the other.
* bugfix: Windows pushing title bar off screenKartik K. Agaram2023-07-101-15/+11
| | | | | | | | | | | I'm learning the hard way that resizing the window is a big deal. Only do this when someone explicitly requests it, otherwise follow LÖVE's defaults. Therefore we're also going to stop trying to be smart when showing the log browser. Leave window resizing to manual operations. Now initialization looks a lot more similar for the run and source apps.
* delete flags that have never been exercisedKartik K. Agaram2023-07-101-4/+0
| | | | Initialization is getting complex, and I'm finding bugs.
* bugfix: preserve window positionKartik K. Agaram2023-07-101-1/+11
| | | | | | | | I just noticed we hadn't got this bugfix for Linux on the main app. How had we not noticed this issue before? Answer: lines.love windows tend to be tall and skinny, and resize must keep the window entirely within the screen. So the window was staying in place just because it happened to be running up against the bottom.
* several bugfixes in saving/loading cursor positionKartik K. Agaram2023-06-081-6/+9
|
* some temporary logging to catch a bugKartik K. Agaram2023-06-011-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bug has been spotted twice: 1. In snap.love, I selected text in one node, then another, and hit: Error: text.lua:789: attempt to compare nil with number stack traceback: text.lua:789: in function 'lt1' select.lua:19: in function 'clip_selection' text.lua:32: in function 'draw' edit.lua:117: in function 'draw' [string "REPL"]:21: in function 'draw' main.lua:152: in function 'draw' app.lua:102: in function <app.lua:84> [C]: in function 'xpcall' app.lua:112: in function <app.lua:111> [C]: in function 'xpcall' Couldn't reproduce. 2. In text.love, inscript selected all text in a small buffer and then clicked outside the text. And got: Error: text.lua:784: attempt to compare nil with number Traceback [love "callbacks.lua"]:228: in function 'handler' text.lua:784: in function 'lt1' select.lua:19: in function 'clip_selection' text.lua:27: in function 'draw' edit.lua:117: in function 'draw' run.lua:136: in function 'draw' main.lua:148: in function 'draw' app.lua:42: in function <app.lua:22> [C]: in function 'xpcall' This is reproducible, and also across forks.
* switch source side to new screen-line-based renderKartik K. Agaram2023-04-031-3/+0
| | | | Also copy over the implementation of links from pensieve.love.
* App.width can no longer take a TextKartik K. Agaram2023-04-011-3/+1
| | | | | In the process I discovered the horrible fact that Text.x allocates a new Text. And it gets called (just once, thank goodness) on every single frame.
* get rid of to_textKartik K. Agaram2023-04-011-6/+2
| | | | | | | | | | | | | I've been misunderstanding what Text objects are. They can render a lot of text with a given line height, word wrap, colors in various places. And I've been creating one for every word :facepalm: Unwinding this will take some time. This is just a first baby step for ad hoc text objects. Turns out I don't need to convert to Text to get something's rendered width, just the Font can do that. Thanks to the LÖVE Discord for educating me: https://discord.com/channels/329400828920070144/330089431379869708/1091535487333826580
* stop reusing cursor locations between filesKartik K. Agaram2023-03-251-1/+2
|
* experiment at avoiding some merge conflictsKartik K. Agaram2023-03-251-0/+13
| | | | https://merveilles.town/@akkartik/110084833821965708
* some minor cleanupKartik K. Agaram2023-03-231-2/+2
| | | | | I can't see the mouse wheel ever setting dx, but it's more obvious now that the editor doesn't support panning left/right.
* mouse wheel supportKartik K. Agaram2023-03-231-0/+5
|
* get typed in keystrokes to show on screen on iPadKartik K. Agaram2023-03-181-0/+7
| | | | Many thanks to Myte for helping test this!
* consistently use App names for methods everywhereKartik K. Agaram2023-03-181-7/+7
|
* more robust state validationKartik K. Agaram2023-03-171-5/+2
|
* hoist out some common settingsKartik K. Agaram2023-01-161-5/+0
|
* bugfixKartik K. Agaram2023-01-061-2/+2
| | | | | lines.love was broken since Dec 23 X-( Didn't get caught because all my tests start at edit, not at main or run. I need 'integration' tests.
* typoKartik K. Agaram2023-01-011-2/+2
|
* fix stale commentKartik K. Agaram2023-01-011-1/+1
|
* make love event names consistentKartik K. Agaram2022-12-231-9/+9
| | | | | 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.
* some debug printsKartik K. Agaram2022-09-171-0/+1
| | | | | | I'm starting to edit the sources from within the app in ernest. First question: why does the file navigation menu skip some files? These prints answer the question.
* more correct absolute path detectionKartik K. Agaram2022-09-111-3/+2
|
* bugfix: path munging on WindowsKartik K. Agaram2022-09-101-2/+3
|
* bugfix: cold startKartik K. Agaram2022-09-031-0/+3
|
* remember window positions across restart/ctrl+eKartik K. Agaram2022-09-031-3/+5
|
* editing source code from within the appKartik K. Agaram2022-09-031-0/+182
| | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* renameKartik K. Agaram2022-05-221-37/+0
|
* beginnings of a test harnessKartik K. Agaram2022-05-221-0/+37
I have no fucking idea what I'm doing. All I know is that there's still too many goddamn bugs[1]. Test motherfucking harness or bust. For starters this is just the default love.run from https://love2d.org/wiki/love.run [1] The following file crashes if you repeatedly press cursor-down: << a b c ```lines ``` x >>
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-14 06:22:24 +0000