Clarification on the problem. Download example file with the link at the bottom.
Simple database. 1 table, 2 fields, 1 script, 1 layout, 1 value list
Two fields are present on the layout twice. Top two are Pop-Up fields, Bottom two are Drop-Down fields.
All fields have the OnObjectSave trigger set to the "Commit" script which has 1 step: Commit Records.
All fields are in the tab order, 1 through 4.
Fat Client behavior:
When clicking either of the top two Pop-Up fields, works as expected. Commit takes place and the pop-up dismisses and nothing is in focus.
When clicking either of the bottom two Drop-Down fields (remember, same Commit script), a virtual TAB keystroke seems to get applied and field focus is forced to the next field in the tab sequence. Commit does NOT exit field focus.
FM Go behavior
When clicking either of the top two Pop-Up fields, field focus to placed in the FIRST tab position. So, if you click the first field, focus STAYS there. If you click the second Pop-Up, focus moves to the first field which is the first tab position.
When clicking either of the Drop-Down fields, focus moves down the tab order to the next field. Commit does NOT exit any field.
As you can see, designing a controlled data entry interface with these anomalies is impossible. Focus is jumping without logic. If I remove all tab stops, behavior on the fat client and Go become the same but still unacceptable. Clicking the Pop-Up fields works as expected. Click, Commit, nothing is left in focus. Clicking the Drop-Down fields results in focus STAYING in the field with the drop-down still expanded causing extra clicks being required to close the drop-down.
Thanks again for investigation/info on this.
Download example file: http://www.mpconnection.com/Test.fmp12
Thanks for the pointer but I don't believe that applies here. I have tried an Exit Script [True] but focus continues to traverse to the next tab in sequence when the drop-down fields are modified rather than all field focus being exited with the Commit Records step.
Set Exit script to [False] as state above and in the link. False saves the data but does not advance to the next field. [True] Advance to the next field.
How does that not apply? That is what you said you wanted.
It must be set to false not true.
Thank you for the follow up. You are correct for fat client behavior. I did not try false until just now. That does clear up fat client behavior.
On FM Go, there is still an issue. The drop-downs behave like the fat client does with a false exit but the pop-ups still reset field focus to the first tab stop. Almost there but with FM Go layouts I tend to use a lot of pop-ups to keep users from accessing the virtual keyboard as seldom as possible.
Thanks again for the extra effort.
You're correct, the popup menu / script trigger (OnOjbectSave) doesn't perform as expect in Go. This may be a bug. You can report this at report an issue at top of this page to have filemaker to take a look.
The documentation states focus will remain with the current field if you exit script with false, and it does not in FileMaker Go.
There is not a built in way to disable the keyboard in Go. You can request a feature at the following link.
The only way I know how to disable the virtual keyboard is with a bluetooth keyboard connect and turned on.