@MartinFelis I have been having hits and misses with these parameters. What exactly do they do?
I noticed that the game occasionally is translated upwards by h pixels, probably to prevent the keyboard from covering the game, but that's not always either.
The optional x/y/width/height parameters are there to tell the system where your text will show up on the screen, so that the on-screen keyboard will (in theory) avoid covering it.
Oooooooh, I see. That's a way more complicated function than I thought.
Technically, it works. However, the function has to run at least once before the game is translated upwards. So what needs to be done:
Tap a designated point to activate the keyboard (the game is not translated).
Deactivate the keyboard.
Tap the designated point again. Only by now, the game is translated to reveal the input box. The function works perfectly everytime from this point.
Is that how it is meant to work?
Are you using the latest nightly build of love-android, or 0.9.1b? I believe there was a bug (my fault) in 0.9.1b where you had to call the function twice for the rectangle parameters to take effect, but it should be fixed in the latest code.
I'm currently on a (minorly) forked version of 0.9.1b. I do not have the source on my PC now, but I will make a pull and confirm this soon enough.