Reading files from the .love always worked. Writing files was broken, but I fixed it (as of a commit a few minutes ago.)T-Bone wrote:Is love.filesystem still untested?
So do I need to put that line in the LÖVE or SDL code somewhere?slime wrote:I'm not sure - I think this is up to SDL, but looking at its code for creating the keyboard on iOS it has this line: "textField.returnKeyType = UIReturnKeyDefault;" which shouldn't make it go away when pressing the return key.
No, SDL's code already contains that line. I was confused because normally that should make the return button behave like you want, but I dug a little deeper into SDL's iOS code and found this:Ivo wrote:So do I need to put that line in the LÖVE or SDL code somewhere?
Code: Select all
/* Terminates the editing session */
- (BOOL)textFieldShouldReturn:(UITextField*)_textField
{
SDL_SendKeyboardKey(SDL_PRESSED, SDL_SCANCODE_RETURN);
SDL_SendKeyboardKey(SDL_RELEASED, SDL_SCANCODE_RETURN);
SDL_StopTextInput();
return YES;
}
If I change the last lineslime wrote:No, SDL's code already contains that line. I was confused because normally that should make the return button behave like you want, but I dug a little deeper into SDL's iOS code and found this:Ivo wrote:So do I need to put that line in the LÖVE or SDL code somewhere?Which is what's causing the text input dialog to always close when return is pressed. Since it's hardcoded into SDL's source, LÖVE can't override it in its own code (and there are situations where you'd want it to auto-close, too.)Code: Select all
/* Terminates the editing session */ - (BOOL)textFieldShouldReturn:(UITextField*)_textField { SDL_SendKeyboardKey(SDL_PRESSED, SDL_SCANCODE_RETURN); SDL_SendKeyboardKey(SDL_RELEASED, SDL_SCANCODE_RETURN); SDL_StopTextInput(); return YES; }
Code: Select all
return YES;Code: Select all
return NO;Thanks! I'll try it when I have the timeslime wrote:If you comment out the "SDL_StopTextInput();" line (line #303 in src/video/uikit/SDL_uikitview.m in SDL's current source) and recompile SDL for iOS it should work as you want, although I haven't tested it.
That's probably because it's a simulator. The emulation of iOS hardware on a computer is (somewhat) computationally expensive so it would be strange if it didn't lag. And lag in an emulator does not necessarily mean it will lag on a real device.xpol wrote:I got a bit lag when running the no game in the iOS Simulator.
The sprites move not as smooth as the PC version.