What am I doing wrong here?
Why is this blue button on the bottom of this layout being chopped off?
This happened to me as well. Has to do with the combination of a Top Navigation part and an object which is anchored to the bottom. It's been reported elsewhere but FileMaker technical support hasn't been able to replicate it. I think the missing piece is anchoring an object to the bottom. Anyhow, I got around it by just using a header part instead.
Could the window be zoomed? If you do a "pinch" gesture, does it "snap" back to 100% and then fit?
It does not appear to be related to zooming. I have tried it both locked and unlocked. (My original setting was 100% zoom locked.)
It appears to be a bug with the "Top Navigation" part.
If I delete "top navigation" or change it to a "header" the layout loads correctly.
I also noticed that if I navigate to a different layout and then come back to this layout that it loads correctly.
What happens if you move the blue button one pixel up ?
rouelf wrote: What happens if you move the blue button one pixel up ?
1 pixel or 10 pixels from the bottom...it does not make any difference.
This is a frustrating bug. I made a duplicate copy of the layout and created buttons that goes back and forth between the two layouts. When the solution loads the layout for the first time the problem exists. As soon as I switch layouts the problem goes away...even when I return to the original layout.
Jaymo wrote: This happened to me as well. Has to do with the combination of a Top Navigation part and an object which is anchored to the bottom. It's been reported elsewhere but FileMaker technical support hasn't been able to replicate it. I think the missing piece is anchoring an object to the bottom. Anyhow, I got around it by just using a header part instead.
Not sure why FileMaker is unable to replicate it. It seems pretty easy to do so.
Have you tried putting the button into a Bottom Navigation part instead of the Body part?
Maybe FMI will be able to replicate it after seeing this post. I'll let them know.
Another observation. Changing the phone's orientation (after the layout loads) corrects the problem.
Jaymo wrote: Maybe FMI will be able to replicate it after seeing this post. I'll let them know.
Great. Please let them know that this FMGO 15 bug only seems to occur under the following conditions:
I sent them the link to this thread. They have confirmed receipt. I will likely never get a response whether it is fixed or not but it has reached it's destination.
One way to get around this issue is to create a blank 'startup' layout (without your button etc), and then have a file options script trigger that runs on 'FirstWindowOpen' which simply goes to the blank layout, does a window refresh, and then goes to the layout you want to appear correctly...
See attached file which replicates your example with the startup script which does just that...
Updated: Just using a Bottom Navigation layout part seems to work just fine as well, with no need for my method outlined above... :-)
Thank you for your post.
I am able to replicate the issue. Thinking it might be hidden behind the bottom toolbar, I created a startup script that hides the toolbar, but the anchored object is still truncated. Besides going to another layout and returning, pinching the layout also works.
Your posts and my sample file have been sent to Development and Testing for review. When I receive any feedback, I will let you know.
pinching the layout also works.
This is something that I suggested that you try way back at the beginning.
Our Testing department is able to replicate the issue. There appears to be an extra unintended scroll area on first layout load. All information has been sent to Development for further review.
Retrieving data ...