AnsweredAssumed Answered

500 pt "invisible" Text Object set up as button size problems.

Question asked by philmodjunk on Jul 9, 2012
Latest reply on Sep 10, 2012 by philmodjunk

Summary

500 pt "invisible" Text Object set up as button size problems.

Product

FileMaker Pro

Version

FMP 12

Operating system version

Windows 7

Description of the issue

Using Conditional formatting to size a text object to 500 pts is a frequently used method for making the button disappear. But when clicking such a button, a rectangle highlights that is the same height as the text object but of much greater width.

When placed in a portal, such an invisible button covers adjacent fields and keeps mouse clicks from putting the focus in the field even when fields are to the left of the button unless fields are arranged to be in front of the button.

Steps to reproduce the problem

Place layout text on a layout and use button set up to convert it into a button.

Give it a conditional format that sets the size to be 500 pts.

Click and hold down the mouse button to observe the area that changes color due to the mouse down action.

Place this in a portal row with the button text object arranged to be the front object and note that the mouse cursor changes to a hand and that you cannot click into fields in the portal row.

Move the fields to the front and note that now you can click into the fields.

Expected result

"Highlight Area" should match dimensions of text object and should not "cover" adjacent fields out side text object dimensions.

Configuration information

First discovered when setting up an "X" as the button for deleting portal rows in a file originally converted to FMP 12 format, then recreated in a newly created FMP 12 file.

Workaround

Use the appearance tab to specify the original text size for the "pressed" state of the button.

TextAsButtonSizeBug.png

Outcomes