Page 1 of 1
Native Field as part of group
Posted: Fri Aug 16, 2024 6:21 pm
by hrcap
Hi All
I hope everyone is well.
I am currently working on improving iOS based layouts and am moving away from standard text input fields to Native Fields.
One issue that I am coming up against is that when the field lays near the bottom of the layout the soft keyboard on screen covers the native field.
How an I create the native field as part of an existing group please, so that the user can scroll the group up to above the soft keyboard?
Many Thanks
Re: Native Field as part of group
Posted: Sat Aug 17, 2024 10:09 am
by Klaus
Since a native iOS field is an OVERLAY on top of your card, I'm afraid it is not possible to "put" it into a group.
Maybe with some ugly tricks, but not right out of the box.
Re: Native Field as part of group
Posted: Sat Aug 17, 2024 11:26 am
by richmond62
Is a native field a widget authored in LCB?
Ouch: the result of asking questions when browsing the Forums from my Android phone;
-
Re: Native Field as part of group
Posted: Sat Aug 17, 2024 11:39 am
by Klaus
Yep, unfotunately only an Android Native Filed is available as a widget and can therefore be place into group.
I already posted an enhancement request for an iOS native field widget, too.
Re: Native Field as part of group
Posted: Sat Aug 17, 2024 12:17 pm
by SWEdeAndy
hrcap wrote: ↑Fri Aug 16, 2024 6:21 pm
How an I create the native field as part of an existing group please, so that the user can scroll the group up to above the soft keyboard?
You'll have to code it in a way that the native field is only created after the group has scrolled up. If needed, you can put a placeholder rectangle (that can be invisible, or look like a field or something) in the group, and after it has scrolled, create the native field and set its rect to the rect of the placeholder.
Re: Native Field as part of group
Posted: Mon Aug 19, 2024 4:35 pm
by hrcap
Hi All
Thank you very much for the feedback. I had a feeling that it may not be possible to place it within a group.
I'll look at making field which appears above the onscreen keyboard like on WhatsApp which should solve the issue.
While im at it do you know when I should get the 'effective working screen rect'.... if I get this at the same time as the iOS field is created it appears that it doesnt give the onscreen keyboard enough time to fully appear on screen and so getting the rect at this point gives a bigger rect than should be.