AnsweredAssumed Answered

Clicking a tab of a tab control does not 'activate' object (working with trigger OnObjectModify)

Question asked by arnoldkegebein on May 16, 2010
Latest reply on May 17, 2010 by raybaudi

Summary

Clicking a tab of a tab control does not 'activate' object (working with trigger OnObjectModify)

Description of the issue

This might not be a bug but an intentional feature. But this behavior creates problems when working with object triggers like OnObjectModify. FileMaker Product(s) involved:FileMaker Pro 10 + 11 Operating System(s) involved:Mac OS 10.5.8 Detailed description of the issue:If a script trigger OnObjectModify is attached to a tab control, then clicking a tab will activate the trigger. But the function Get( ActiveLayoutObjectName ) used in the trigger script will not return the name of the tab object, even when all tabs have their individual object names. Actual, clicking a tab will not activate the tab control like moving the object focus with the tab key would do. Still, there is an object, that fires a trigger, but I cannot get the objects name. This behavior is kind of understandable, because not the trigger is not assigned to each single tab but the tab control. Unfortunately, you cannot assign an object name to a tab control, only to each single tab. Exact steps to reproduce the issue:Create a tab control with at least two tabs, giving all tabs individual object names.Assign a trigger script for OnObjectModify to the tab control object.The trigger script should include a step: Show Custom Dialog [Get ( ActiveLayoutObjectName )]In browse mode click on the tabs.Expected Result:The object name of the clicked tab should be shown in the dialog box. Actual Result:The dialog box is empty. Any workarounds that you have found:None. Possible solutions in future FileMaker versions:A build-in function Get( TriggerObjectName )Allow the naming of tab control objects (not only the individual tabs)Activate the tab object when clicked on it. 

Outcomes