Keyboard in iOS 15.x

[Mark Smith]

Hi Panos, 

I discovered the “extra” line at the top of the keyboard was called “predictive” in the keyboard settings. Turning predictive off removes the extra line, so that solved the immediate problem, but not the longer term one (which can only really be fixed by either “pinning" the header bar during a “pan” or knowing where the top of the keyboard is for appropriate DG resizing.) I'll make a feature request in the QCC. 

Merry Christmas and Happy Holidays to all,

Mark


> On Dec 23, 2021, at 5:28 PM, Mark Smith <marksmithhfx at gmail.com> wrote:
> 
> Thanks Panos, I appreciate the quick response. That works reasonably well except the card has a header bar and using the “pan” option moves the header bar off screen as well, which unfortunately hides some important header bar controls. If we could “stick” the header bar while panning the dg (so it visually looks like it is sliding underneath the header bar) that would be the best solution. I might try and see if there is a way to do that. Otherwise for now I’ll just hard code a resize of the dg when the keyboard is activated and adjust the code using the new iPhoneDeviceModel function to fine tune it for different screen sizes. 
> 
> You should probably be on vacation now, so enjoy your well deserved time off!!
> 
> Mark
> 
> 
>> On Dec 23, 2021, at 3:25 PM, panagiotis m via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> Hello Mark,
>> 
>> What about using:
>> 
>> mobileSetKeyboardDisplay "pan"
>> 
>> See the dictionary for more details.
>> 
>> Cheers,
>> Panos
>> 
>> 
>> 
>> On Thu, 23 Dec 2021 at 17:08, Mark Smith via use-livecode <
>> use-livecode at lists.runrev.com> wrote:
>> 
>>> It seems the keyboard in iOS 15 has gained some height and that is causing
>>> a problem.
>>> 
>>> Scenario. My UI is primarily a datagrid. Fill it with 8 items and the next
>>> one added will cause the keyboard to cover the row. The previous solution
>>> has been to redraw the datagid so it occupies the space above the keyboard
>>> (and then scroll the new line into view). This worked fine as long as the
>>> KB always occupied a fixed amount of space (height). The new one in iOS 15
>>> appears to be approximately 1 row of keys taller, this row being filled
>>> with blank slots for word guesses while you type (an option I would not
>>> even know how to make use of).
>>> 
>>> Solutions: one option is to simply redraw the datagrid to be above the new
>>> keyboard height. Problem is I have been hard coding this (ie. changing the
>>> bottom of the keyboard from 452 (activated) to 613 (deactivated) as
>>> required). This is less than ideal because as I have now witnessed in iOS
>>> 15.x the keyboard can expand to have 1 or 2 extra rows above the keys. ie.
>>> the size/height of the keyboard is now dynamic. Ideally I would be able to
>>> query the height of the keyboard, or the amount of available screen space,
>>> so that I could adjust the bottom of my datagrid appropriately.
>>> 
>>> Has anyone else been looking into this issue and how have you resolved it?
>>> 
>>> Thanks
>>> Mark
>>> 
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>