nativefs doesn't work on iOS since LÖVE v11.5, so I should stop using it
at least on forks for mobile devices.
I still use it in a couple of cases:
* on a file DELETE request from the driver
* when trying to write modifications from the driver to the original
location
On my phone the tiles are really tiny, and fat-fingering seems to be at
least 50% probable if not more. And if I accidentally tap on a crate I
can't even try to tap on a clear space until I clear the location of the
crate. This change lets me more easily use at least the path-finding
solver for moving just the player around.
Current design choices:
* Unstashing doesn't delete the file. You have to bump down to the
scratch screen for that.
* Can't unstash if the file already has local modifications. Decide
whether to revert or stash them.
I'm scaling down my ambitions. Stashed files can't have notes attached.
I think that encourages a higher scale of development on such apps than
is currently justified, given you're liable to lose all your work if you
upgrade LÖVE.
New plan: just name stashed files with a numeric suffix.
The remaining open question is now around unstash. Should unstash copy
or move?
We can create them and see them on the file dialogs, but not yet load
them back.
I want stashed files to remember the original filename. I think that
implies the ability to add a note to them. But I don't yet know how to
represent the note on disk.
And this creates cascading questions, like should editing a stash file
continue to modify it or create a new version? How to create a new
version? Should unstash copy or move?
Scenario: every once in a while I try to paste on my phone (in the
overflow menu) and fat finger and tap 'clear' next to it instead.
I could try adding space between the buttons in the overflow menu, but
that creates cascading issues of how it should look. Swapping these two
buttons is a hacky way to ensure that buttons that mutate the buffer
are never side by side.
I originally made this change to keep the next/prev buttons from
overwriting the search bar. But now the dropdown menu up top gets
overwritten by the scrollbars! You can only see it if the window width
is just right, as happens on my phone.
I could fix this perfectly, but at the cost of some code complexity.
Just take that slight visual ugliness for now, it doesn't seem to impede
anything.
Kartik K. Agaram