Is this anyhow related to this report?
Horizontal Screen area on iPad
"As you can see in the picture for Layout-Mode, the layout is tailored to end on the right side at position 320px.
Yes and no.
No, in that I'm on a PC, not iOS.
Yes, in that the issue (I think) is essentially the same: a user should never see objects that are placed outside the layout's defined boundary.
Do you know that a object outside may appear if it just touches the border?
Could you upload a screenshot of layout-mode that shows border AND object outside?
A screen shot is tricky, because as I said, the objects are only displayed for a second, then the screen redraws and they vanish as they should.
If you mean a screen shot in layout mode, I could, but to what end? I assure you, the objects in question are not even close to touching the border.
It's definitely a bug.
Thank you for the post.
To attempt to replicate this behavior:
1. Created new database.
2. Added two fields.
3. Created a layout 888 pixels X 888 pixels
4. Placed one field in the visible layout space and one field outside the visible layout area.
5. Entered browse mode, sized the window smaller than 888 pixels.
6. Sized the window to larger than 888 pixels.
While in browse mode, I never once saw the field outside of the layout space. I quit and reopened the file and tested multiple times on both Windows 7 and Windows XP. I also tried with different anchor orientations for the fields.
How often does this occur? Perhaps, I am missing a step to replicate?
Is it possible that you saw this underst circumstances that would slow the window refresh down by a large factor? Such as when remotely accessing the DB from a location outside the server's network and/or from an iOS client?
Can you see this from more than one layout?
Got a demo file that illustrates it that you can upload to a file sharing site such as drop box?
My guess would be that your intuition is correct: this is a complex layout, lots of objects, tabs, portals, conditional formatting etc.; a large database, about 400,000 records and hundreds of fields in the main table (messy medical data); and served over a WAN (albeit a fast one).
So it may be atypical and hard to reproduce, but still a bug. IMHO kind of a serious one.
It seems like FileMaker 12 has issues in lagging screen refresh in general. This may be just another example.
Thanks very much for testing it. I appreciate your taking the time. Sorry I cannot provide you a sample file right now.