Commit in OnObjectModify for Popup Menu does not exit field in FMGo 12 (6 Comments)

Issue report by Troy Meyers

Product

FileMaker Go

Version

iPhone and iPad Go 12.0.3

Operating system version

iOS 5.1.1

Description of the issue

Unlike desktop FileMaker Pro 11 & 12, and iPad Go 11, when a Popup-menu field has a value chosen, when the OnObjectModify script is executed, which consists simply of Commit Record [Skip..; No dialog], the field is NOT exited, and the large touch-style menu is still displayed (or is redisplayed, not sure which).

In iPad Go 11, and in any desktop FileMaker Pro, this is not the behavior. Instead, the record is committed, and the menu does not re-display... which is the expected behavior.

Steps to reproduce the problem

Try the sample file attached. It has an icon-displaying container calculation (which cannot be entered) sitting on top of a text popup menu that is reduced in size so that the text does not show, unless it's selected. Clicking/touching the icon location actually brings up the menu instead. Choosing a value is supposed to commit the record, and exit the field, displaying the new calculated icon.

Expected result

Clicking/touching the icon location which activates the underlying popup menu allows a text choice, and when it is made, the menu should disappear, the record commit, and the new icon (by calculation) is shown.

This does work fine in FileMaker Pro 12 (desktop), and did work in iPad FMGo 11.

Actual result

Clicking/touching the icon location which activates the underlying popup menu allows a text choice, and when it is made, instead of the menu should disappearing, it either continues to display (or is redisplayed immediately), presumably after the commit. This continues to obscure the new icon.

Commit actually does occur, but the field is not de-selected.

This occurs in FMGo 12 for both iPad and iPhone

Exact text of any error message(s) that appear

none

Configuration information

The simple test file supplied is sync'd to the iOS device, but the actual file that has the problem that prompted this posting is hosted by FMS 12.

This is how I know that the commit actually does occur when a choice is made... other clients immediately see the updated value.

Workaround

none