Get Keyboard Height

Solar2D General Questions/Discussion
#1

I have had a search of the forums but can’t seem to find anything.

When the native keyboard shows it is hiding the bottom 3 textboxes within my app. This is not a problem as I can move the textboxes accordingly using the keyboard “Began” event, however, I have a slight problem.

How do I know where to move the textboxes too e.g. the keyboard height.
The Iphone keyboard height I think is about 216pixels in portrait, but will this be the same on ipad, and what is it on Android?

Has anyone else come across this problem and perhaps have a solution?
Any help would be greatly appreciated.

[import]uid: 103163 topic_id: 19529 reply_id: 319529[/import]

#2

We can’t get the keyboard height, no. That is an interesting point to bring up though, it would be worth looking into the differences in keyboard heights.

If I come across anything useful I’ll get back to you :slight_smile:

Peach [import]uid: 52491 topic_id: 19529 reply_id: 75431[/import]

#3

Thanks Peach!

I think in the meantime I will check which OS it is and use the information I have for IOS and then take a rough estimate for Android (higher than needed).

If I find out anything more useful than the above I will post back here [import]uid: 103163 topic_id: 19529 reply_id: 75448[/import]

#4

+1 this would be a pretty useful thing.

@Peach
Is there a list of keyboard heights for iOS devices? I mean unlike android, we would have just 2 or 3 heights for iPhone and iPad right? [import]uid: 64174 topic_id: 19529 reply_id: 120643[/import]

#5

+1 this would be a pretty useful thing.

@Peach
Is there a list of keyboard heights for iOS devices? I mean unlike android, we would have just 2 or 3 heights for iPhone and iPad right? [import]uid: 64174 topic_id: 19529 reply_id: 120643[/import]

#6

This would actually be pretty useful to know, could we maybe compile a list of known heights?
It’s not exactly future proof but if we can at least make a table with all the devices we know now, it’s probably not too much of a stretch to approximate future devices. [import]uid: 84115 topic_id: 19529 reply_id: 131555[/import]

#7

Another options would be to make your own keyboard?

I done this for a number-pad, mainly so I had control over the design of it [import]uid: 62706 topic_id: 19529 reply_id: 131562[/import]

#8

I considered that, but at the moment I don’t really need it to look any different to the native keyboard. So I’d rather use a keyboard that I can be reasonably sure will work - not that I’m saying one that I made wouldn’t work :stuck_out_tongue:
[import]uid: 84115 topic_id: 19529 reply_id: 131563[/import]

#9

Yeah, for the majority situations, the native keyboard is perfect. [import]uid: 62706 topic_id: 19529 reply_id: 131565[/import]

#10

This would actually be pretty useful to know, could we maybe compile a list of known heights?
It’s not exactly future proof but if we can at least make a table with all the devices we know now, it’s probably not too much of a stretch to approximate future devices. [import]uid: 84115 topic_id: 19529 reply_id: 131555[/import]

#11

Another options would be to make your own keyboard?

I done this for a number-pad, mainly so I had control over the design of it [import]uid: 62706 topic_id: 19529 reply_id: 131562[/import]

#12

I considered that, but at the moment I don’t really need it to look any different to the native keyboard. So I’d rather use a keyboard that I can be reasonably sure will work - not that I’m saying one that I made wouldn’t work :stuck_out_tongue:
[import]uid: 84115 topic_id: 19529 reply_id: 131563[/import]

#13

Yeah, for the majority situations, the native keyboard is perfect. [import]uid: 62706 topic_id: 19529 reply_id: 131565[/import]