How can I keep the iPad keyboard fixed on the layout without it disappearing?

Hi all,

I am encountering an issue where, when a visitor searches for the host, the script refreshes the Layout, causing the iPad keyboard to disappear after a second. This refresh disrupts the user experience and is not ideal for visitors.

If anyone has recommendations or a solution for this issue, I would appreciate your support.

script on object modify

Don't refresh, and especially don't flush the cache.

You usually don't even need the commit or refresh if you are wanting results to update.

Try the following script step instead:

Set Field [ Get ( ActiveFieldContents ) ]

This step will set the current field to itself, which is often enough to refresh a relationship that might be displaying results based on the field you've typed in.

2 Likes

Thank you for your support. Unfortunately, the script is not working after adding the Set Field [ Get ( ActiveFieldContents ) ] step.

If you add the script step "Enable Touch Keyboard [on]" maybe that would work? I'm not in a position to test this right now, so just a suggestion.

Unfortunately, Same the issue :slightly_smiling_face:

When you change modes (Browse/Layout/Find/Preview), all the popover style windows will close, including the keyboard. A scripted enable KB step AFTER the find completes, should force the keyboard open.

After the 9 step i put enable keyboard on ?

That's the (untested) thought process. It might be the solution.... TBD

It is kinda like when you have a popover window open and enter FIND mode, expecting to enter data into the popover as part of the find, and the popover is closed. A Go To Object for a named object within the popover window, placed after entering find mode, forced the popover window open.