about summary refs log tree commit diff stats
path: root/edit.lua
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2023-03-231-0/+14
|\
| * some minor cleanupKartik K. Agaram2023-03-231-1/+1
| | | | | | | | | | 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/+14
| |
* | Merge lines.loveKartik K. Agaram2023-03-181-1/+1
|\|
| * move default file locationKartik K. Agaram2023-03-181-1/+1
| | | | | | | | | | | | | | | | This works better on mobile platforms while seeming about as useful anywhere else. I've verified that anyone who already edited a file will continue to use its path from settings.
* | Merge lines.loveKartik K. Agaram2023-03-171-3/+8
|\|
| * bring a few things in sync between run and sourceKartik K. Agaram2023-03-171-1/+4
| |
| * bugfix: disallow font size of 0Kartik K. Agaram2023-03-171-2/+4
| | | | | | | | Thanks Mikoláš Štrajt.
* | Merge lines.loveKartik K. Agaram2023-03-171-0/+16
|\|
| * more robust state validationKartik K. Agaram2023-03-171-2/+24
| |
* | Merge lines.loveKartik K. Agaram2023-02-091-0/+1
|\|
| * bugfixKartik K. Agaram2023-02-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | scenario: press ctrl+f, type in a string hit down arrow if needed until the screen scrolls press enter click with the mouse somewhere Before this commit the app would crash because cursor was above screen top.
* | Merge lines.loveKartik K. Agaram2023-01-281-0/+2
|\|
| * wait a little to flush disk before quittingKartik K. Agaram2023-01-281-0/+2
| | | | | | | | | | | | | | I've been noticing in pensieve.love in particular that once a month or so I lose data if I quit immediately after typing in something. Nothing major, just the odd link between notes which leaves things in an inconsistent state. Let's see if this helps.
* | Merge lines.loveKartik K. Agaram2022-12-241-1/+1
|\|
| * bugfixKartik K. Agaram2022-12-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | Scenario: make some edits, select some text, make some more edits. Press ctrl-z. Before this commit, undo would stop at the point of selection and previous edits would become unreachable. After this commit, both ctrl-z and ctrl-y seem able to span the point of selection.
| * typoKartik K. Agaram2022-12-241-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-12-231-21/+21
|\|
| * consistent names in a few more placesKartik K. Agaram2022-12-231-4/+4
| |
| * make love event names consistentKartik K. Agaram2022-12-231-19/+19
| | | | | | | | | | 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.
| * require editor margins to be intsKartik K. Agaram2022-12-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Not directly relevant here, but forks of this project that permit zooming can run into weird glitches if margins are not a whole number of pixels. I'd always assumed a type system that divided ints into floats was strictly superior, but now I have experienced a situation where requiring ints isn't just a compromise for the underlying CPU implementation. Particularly since Lua's print() silently hides really tiny fractions.
| * bugfix in changing shape mid-strokeKartik K. Agaram2022-12-121-2/+5
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-1/+6
|\|
| * bugfix: naming points in drawingsKartik K. Agaram2022-12-121-1/+6
| | | | | | | | | | | | | | | | | | We had a regression since commit 60e1023f0 on Nov 27. Turns out we do need the ancient hack after all. But no, we won't go back to the hack. It's a simple problem to fix right. And while we're at it, we'll fix the test harness to be more realistic so it would have caught this problem.
* | Merge lines.loveKartik K. Agaram2022-11-271-1/+1
|\|
| * bugfixKartik K. Agaram2022-11-271-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-11-191-1/+4
|\|
| * ctrl+a: select entire bufferKartik K. Agaram2022-11-191-1/+4
| |
* | purge unused button infrastructureKartik K. Agaram2022-11-051-6/+0
| |
* | Merge lines.loveKartik K. Agaram2022-11-031-2/+2
|\|
| * stop tracking wallclock timeKartik K. Agaram2022-11-031-2/+2
| | | | | | | | We only need time differences.
* | Merge lines.loveKartik K. Agaram2022-09-101-1/+1
|\|
| * bugfix: path munging on WindowsKartik K. Agaram2022-09-101-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-09-071-1/+4
|\|
| * self-documenting 0 Test_right_marginKartik K. Agaram2022-09-071-1/+4
| |
* | Merge lines.loveKartik K. Agaram2022-09-051-3/+5
|\|
| * support drawings in the source editorKartik K. Agaram2022-09-051-3/+5
| |
| * editing source code from within the appKartik K. Agaram2022-09-031-9/+0
| | | | | | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* | editing source code from within the appKartik K. Agaram2022-09-031-5/+0
| | | | | | | | integrated from pong.love: https://merveilles.town/@akkartik/108933336531898243
* | Merge lines.loveKartik K. Agaram2022-08-241-0/+1
|\|
| * infrastructure for caching LÖVE text objectsKartik K. Agaram2022-08-241-0/+1
| |
* | Merge lines.loveKartik K. Agaram2022-08-231-12/+16
|\|
| * flip return value of button handlersKartik K. Agaram2022-08-231-2/+1
| | | | | | | | | | | | This is compatible with Javascript, and it also seems like a better default; when people forget to think about return values in click handlers, they should be consumed.
| * stop putting button state in a globalKartik K. Agaram2022-08-231-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Symptom: a test (test_click_to_create_drawing) started randomly failing after I inserted a `return` 2 commits ago. Cause: my tests call edit.draw, but button handlers only get cleared in app.draw. So my tests weren't clearing button handlers, and every call to edit.draw was accumulating states. Still unclear why those were going to different state objects after the `return`, but anyway. I'm not going to understand every last thing that happens when things go wrong, just guarantee they can't go wrong. And the way to do that is to decentralize button handlers to each state that receives them. The State object in buttons.lua doesn't have to be Editor_state. It just has to be some table that provides a Schelling Point for shared state.
| * allow buttons to interrupt eventsKartik K. Agaram2022-08-231-1/+5
| | | | | | | | Most button onpress1 handlers will want to return true.
| * distinguish consistently between mouse buttons and other buttonsKartik K. Agaram2022-08-231-11/+11
| |
* | Merge lines.loveKartik K. Agaram2022-08-181-0/+2
|\|
| * subsection headings in a long switchKartik K. Agaram2022-08-181-0/+2
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-5/+3
|\|
| * simplify cursor-on-screen checkKartik K. Agaram2022-08-171-5/+3
| |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 15:37:32 +0000