On iOS the soft keyboard can not use ESC etc. #2
Comments
I'm thinking for another solution - on screen controls. They will make you able to use arrows also. What do you think? Another option is to add |
Or another thing, I probably should do, is implement my own on screen keyboard. Yep, will do that. |
I think an |
The only thing is, you won't be able to exit 😆 |
We can add an button icon on top of editor like other sprite/music.. icons, click it will exit. I will try to finish it, wait a few minutes... |
Good job! I only finished to add the command edit. |
It works very well on mac and iOS, but a strange thing ,on my mac and iPad, the exit icon can not see. |
Hmm, try to replace it's position in I don't have any mobile devices, so I can't check it, sorry. |
The close function is ok, only the icon can not display, so we need not change the cords of x and y, they are correct. |
Hm, did you change neko.n8? If so, override it with a new one. |
Pull it get the message of :
Then rm it and clone again, but still no icon... |
Hm, then edit neko.n8 your self, and add icon at slot 13. |
The thing with this is, that neko8 has two save dirs: project root dir and another dir hidden in app data (you can open it with |
I am a newbie of pico-8, so I need to learn what is the slot 13, after get it clear, I will add the icon manually :) Now I will study the whole code of neko-8 and try to port it to a Raspberry Pi + LCD, then we can get an entity neko-8! |
I recommend you to have a look at this API manual: https://neko250.github.io/pico8-api/ Neko8 doesn't implement all calls just yet and it doesn't support memory at all. But you can look up all available API calls here: https://github.com/egordorichev/neko8/blob/master/main.lua#L1069 |
OK, thanks, I will go to read the docs. |
Merge pull request #21 from FreeBlues/master
On iOS, the default soft keyboard called with love2d can not use the ESC or CTRL key, we can not launch the Editor. So I add some ugly code directly in the function love.touchpressed(), it can launch the Editor on iOS, see below:
The text was updated successfully, but these errors were encountered: