| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Thanks Garvalf for improving my understanding here relative to
https://love2d.org/forums/viewtopic.php?p=257623#p257623 back in Nov
2023.
Levels of understanding:
- never trigger both textinput and keypressed, so never trigger
textinput if a modifier is down
- wait, shift is a modifier. Ok, ignore modifiers except shift.
- ctrl can never be triggered anyway. get rid of the whole modifier
check.
- wait, alt-c does trigger textinput('c')
- allow textinput if a modifier changes the key being pressed
- and now: turns out azerty requires shift to turn keypress '1' into
textinput '1'. Better understand that layout and others. Textinput
events can be triggered by either shift or altGr combinations. altGr
isn't directly represented by LÖVE. It's usually the right alt key.
There are probably devices out there that send other key combinations on
altGr. I'll wait for people to chime in who can help test on those
devices. In the fullness of time this probably requires some
configuration:
[ ] altGr is right alt
[ ] altGr is ctrl+alt
[ ] disable altGr
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
scenario:
- position cursor at start of buffer
- press backspace
- press ctrl-z to undo
Before this commit the editor would crash, because an undo event had no
before.
|
| |\| |
|
| | | |
|
| |\| |
|
| | | |
|
| | | |
|
| |\| |
|
| | | |
|
| |\| |
|
| | | |
|
| |\| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I disabled it 2 days ago to fix this bug: with LÖVE 12 (both a release
from Feb and a recent release) on Linux, every successive invocation
would shrink the window.
However, in disabling it I introduced a new bug: Carousel ended up with
a huge resolution on my phone and text became miniscule.
Just undo for starters.
|
| | | |
|
| |\| |
|
| | | |
|
| | |
| |
| |
| |
| | |
It will require lots of changes, and I don't know how to think about it
yet.
|
| | | |
|
| | |
| |
| |
| | |
Both are for desktop only. Not guaranteed to work on mobile.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I've resisted this for some reason all these years, but finally
encountered a situation that requires it:
$ love ./
This runs the app, but with an identity of 'lovegame'. So all new
save dir, etc.
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
I just noticed that the is_touch arg in mouse handlers is extremely
useful for arbitrating between events on a mobile device. And I'd
totally forgotten about its existence X-(
|
| | | |
|
| | | |
|
| |\| |
|
| | | |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
The culprit is an ambiguously named helper. put_cursor_on_next_text_line
is not supposed to move to next line if the current line is text.
|
| |\| |
|
| | |
| |
| |
| |
| | |
I'm still using these to periodically reassure myself about the state of
lines2 and its descendants.
|
| |\| |
|
| | | |
|
| | | |
|
| |\| |
|
| | | |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| | |
Avoid accidental side-effects.
|
| | |
| |
| |
| |
| | |
This is a regression. Scenario: search for a string, then backspace
until it goes empty.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This one is ancient and it affects every single one of my forks,
including the whole lines2 lineage. The corner case: searching for empty
string.
In the process I've also cleaned up edit.check_locs on initialization to
only modify cursor if it can find a legal place for it.
In general I should be more careful about mutating the cursor. Just
adding 1 to it is irresponsible.
|
| | |
| |
| |
| | |
Ported from bugfix of 2024-06-23.
|
| |\| |
|
| | | |
|