Occasionally, you hit certain issues within FileMaker development where you're just stumped as to why you can't do something. Let's take a super simple example like being able to show and hide a button based on having selected a given portal row. How do you know when the user is within the portal? How do you know when they've left?
Think it's easy? Try to solve this issue without watching this video first. You'll quickly find out, that because of how FileMaker's "event model" works, known as script triggers, that some times things happen when you want and other times they don't. And, ultimately, you don't have control. FileMaker picks the Pre vs. Post.
Unless, that is, you get creative with how you solve this particular problem. In the case of Pre vs. Post script triggers, it is possible to extend how FileMaker behaves. In this video, I showcase how to solve the simple problem of showing and hiding a given button when a portal row is selected. It's a bit of a trick, but it can certainly be done.
Additionally, if you don't yet know the value of knowing when a user has a given portal row selected then you'll learn that lesson as well by watching this video!
Click the title or link to this article to view the video.