2 Replies Latest reply on Sep 13, 2016 11:35 AM by jsciarra

    Hide Object Calculation Disappears After Attaching Script to Object

    jsciarra

      Product and version FM Pro Advanced 15v01

      OS and version - Mac OS X El Capitan, Windows 7

      Hardware Mac with VMWare

       

       

      A graphic object that has hide object logic associated with it loses the ability to see and access that logic after you attach a script to the object. Removing the script does not make it reappear and the logic continues to operate regardless. Worse you can add another calculation and it shows two hidden object icons and does not override the hidden logic.

       

      There is an attached file demonstrating this bug.

       

      J. Sciarra

      Colibri Solutions

        • 1. Re: Hide Object Calculation Disappears After Attaching Script to Object
          TSGal

          jsciarra:

           

          Thank you for your post.

           

          When you group an object with a button, the button information takes precedence.  If you ungroup the button from the object, you will then see the Hide object when calculation.  Therefore, either add the Hide object when condition to the button, or add the graphic object to the Button Setup and reference the object when you setup the Button.

           

          TSGal

          FileMaker, Inc.

          1 of 1 people found this helpful
          • 2. Re: Hide Object Calculation Disappears After Attaching Script to Object
            jsciarra

            Thanks TSGal. The problem for us was the following trap. There are two different behaviors interacting in a way that is very confusing. By invoking the "Button Setup" and associating the graphic object with a script you are effectively grouping it at that time. If you go back in to the button setup and then choose "Do Nothing" it remains grouped and effectively hiding the the calc. You are correct in that the literal "Ungroup" command will then set it back to it's original state and reveal the calc. Very helpful and good to know. This behavior then is not a bug perhaps, but is non intuitive and could be rectified programmatically at some point in the future. On other hand understanding it makes it much less of a big deal. Appreciate the response and clarity.