AnsweredAssumed Answered

Transparent buttons are all broken in FileMaker 12

Question asked by scottworld on May 18, 2012
Latest reply on May 23, 2012 by philmodjunk

Summary

Transparent buttons are all broken in FileMaker 12

Product

FileMaker Pro

Version

12.0

Operating system version

Mac OS X 10.6.8

Description of the issue

FileMaker 12 has broken all of our transparent buttons from FM11 and earlier.

We often create transparent boxes (no border & no fill), arrange them so that they are at the front of all other objects, and then assign a button to those transparent boxes.

This enables us to do all sorts of amazing things, such as putting one gigantic button horizontally across all the fields in list view, so when the user clicks on the button, they are taken to the detail view of the record that they just clicked on. But because the button is transparent, they can still see the fields through the button so they know what they're clicking on.

IN ORDER FOR TRANSPARENT BUTTONS TO WORK, they MUST BE AT THE FRONT OF ALL OTHER OBJECTS. Otherwise, the user ends up clicking on whatever is visible through the button instead of the button itself.

BUT FILEMAKER 12 HAS BROKEN ALL OF THIS.

In FileMaker 12, in layout mode, we developers CANNOT SELECT OBJECTS THAT ARE BEHIND THE TRANSPARENT BUTTON. IN ORDER FOR US DEVELOPERS to select objects behind the transparent button in layout mode, we have to SEND THE TRANSPARENT BUTTON TO THE BACK. This defeats the entire purpose of the transparent button, because then in browse mode, the button is NO LONGER CLICKABLE because it is behind everything else. So we developers have to SEND THE BUTTON TO THE BACK IN LAYOUT MODE, then SEND THE BUTTON BACK TO THE FRONT before we return to browse mode.

So FileMaker just made our lives a million times more difficult in FileMaker 12, because now we have to jump through all these extra steps that we never had to jump through before. In the past, in LAYOUT MODE, we were able to click on objects that were visible through transparent objects.

Please revert this behavior back to how it used to be.

Outcomes