5 Replies Latest reply on May 6, 2013 5:26 PM by wsvp

    Bug? — Images in Portal Rows


      FM12 Advanced

      OS X 10.8.3


      If I use the inspector and specify the coordinates of an image in a portal row, the image only shows on the first line. If I move the image up one point and then down one point, it will then show on all portal rows. I'm assuming this is a bug. Anyone else experiencing this? See attached screenshots.



        • 1. Re: Bug? — Images in Portal Rows

          Forgot to add that I'm on FMA 12.0v4

          • 2. Re: Bug? — Images in Portal Rows

            I have this problem on Windows 8 as well, but I have had the issue with both image and text fields.  Also experienced the bug if I copy the portal to another layout.  After paste, I have to select the row, reduce the object height to one point smaller, then one point larger again.

            • 3. Re: Bug? — Images in Portal Rows

              Actually its probably intended behavior. (I'm sure someone desires it).


              In FMP12 you can now place an object above a tab and have it floating above/outside of the tab layer. Moving it one pixel is the method used to move the object into the tab layer.


              If your Portal is in a tab you could be expieriencing this behavior.


              If your portal is no in a tab then possibly the original alignement of the field was not fully within the portal.

              • 4. Re: Bug? — Images in Portal Rows

                My portal is in a tab, so this is probably the case.

                • 5. Re: Bug? — Images in Portal Rows

                  The tab is not specifically the issue...


                  This likely has to do with the Parent Child relationship established between objects.  In FM11 and prior portals did not encapsulate the objects within them, Like Tabs do.  In FM12 Portals now link the objects as children and the objects move with the portal.  It probably has to do with the object layering,... when you physcally drop the object on the Parent (portal or tab) it knows to link it as a child.  Changing the position value of an object outside the parent/child link, in the inspector does "not" establish the Parent/Child link.