Tab Script Triggers - Revisited
A few articles back, I discussed the use of conditional formatting to facilitate the use of triggering scripts when switching tabs. While this was identified as being somewhat specific to tab panels, it actually applies to any time a new view is rendered - be that a layout or tab panel switch. Think of it as an "On Layout Show" or "On Screen Redraw" event.
In the original article, I proposed the solution of keeping all corresponding scripts for each named tab in one text field. The limits to that approach as such that other actions specific to that view must be intermingled with the scripts for the tabs - within the same text block.
While working on the solution in my Zero to Awesome series, I modified my approach and also implemented one critical element - a trap for not triggering a script when a widow is resized and re-rendered. In this video you'll learn the power technique of triggering scripts when switching to any new view. You control when scripts are triggered and what happens in the interface.
Comments
very fine indeed, very fine,
my friend, that is a very fine technique indeed.
i'm going to use it considerably for those tricky jobs like you say. Just used it to fix BackMagic's screen refresh problem if you go to a new tab and the forward button is lit, it remains lit, whereas a wee screen refresh sorts it out. And you only want to do this the once… And now i have a very handy little tool to use for that… fine stuff.
Blessings, t
PS a sample file would have helped, but got there in the end.
Sample file on previous article
Sorry, I should have pointed out that the file with examples exists on the previous article.
http://www.filemakermagazine.com/videos/zero-to-awesome-using-a-history-table.html
-- Matt Petrowsky - ISO FileMaker Magazine Editor