Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8003 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Sorta. (FileMaker's common answer!)

You can store the button's graphic in a calculated container field. If the calculation = true, the graphic will display. You can then overlay the graphic with a transparent box that is connected to your buttons script.

The downside to this is that you will need to have the same logic in the script to determine if the button is showing or not. If the user happens to click where the button is, when it's not showing, they will see the button "press" but your script will not run.

There is also another method that involves self-relations and portals. This method is much more complicated, but it actually "removes" the button object from the layout and cannot be clicked.

Posted

There is another way, maybe. You can put a button into a 1 line portal controlled by a relationship. If you can make the relationship work, i.e. indexed, the button will appear if the relationship is true, and disappear when it's false.

This topic is 8003 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.