| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
integrated from pong.love via text.love:
https://merveilles.town/@akkartik/108933336531898243
|
| |/
|
|
| |
integrated from pong.love: https://merveilles.town/@akkartik/108933336531898243
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
The published version of lines.love was broken for almost an hour. The
cursor would render one position to the right of where it really is. To
fix it, this commit rolls back 26ba6e4e5a71. There doesn't seem a good
way to test it.
|
| | |
|
| |
|
|
|
|
|
|
| |
Still lots to do, but the eventual hope is that this will make this
project's code easier to reuse from other LÖVE projects.
One gotcha: even as we start putting code more aggressively into nested
tables, tests must remain at the top-level. Otherwise they won't run.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
State changes when inserting return are now in sync with other
characters.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also ensure we autosave.
|
| | |
|
| | |
|
| |
|
|
|
| |
I found some code in the process that seems unreachable. Some chance of
a regression here..
|
| | |
|
| |
|