Filemaker pro 11 tabs1/9/2023 Once you know all that, keeping tabs on your tabs (sorry) is easy. * The `OnObjectSave` trigger never fires for a tab control. ![]() * The `OnObjectKeystroke` trigger fires when the tab control has focus and you press any key on the keyboard. In other words, when you tab *away* from it. * The `OnObjectExit` trigger fires when the tab control *loses* focus. You can see a tab control with keyboard focus here: This happens when it is in the tab order and you tab to it (so a tab gets the thick black border). * The `OnObjectEnter` trigger fires when the tab control gets keyboard focus. This is probably the most useful trigger for tab controls. * The `OnObjectModify` trigger fires whenever the user switches to a different tab. It is unfortunately not entirely obvious, but Script Triggers work with tab controls. We’ll show you how to solve this problem quickly and easily using script triggers. In the end, we’ll also revisit a common FileMaker problem: tabs switch when you switch layouts. In this article we’ll show you how to run scripts when users switch tabs on your tab controls. ![]() ![]() You might, at first, think triggers are limited to layouts and fields, but it turns out your triggers can fire with all kinds of objects. ![]() FileMaker 10’s new Script Triggers feature just keeps delivering.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |