Can you do this?
Enter layout mode
Bring up button setup for the third button (Clients & Contacts) and post a screen shot of what is entered for the button's text label?
I can't replicate that. Can you paste that button bar into a new file and see if it behaves the same? If you want to attach the file with just the button bar, we may be able to help diagnose it better.
Here is a screenshot of the setup for button 3. By the way, I checked to see if it might be the popover causing the issue, but it's not — button 8 (Windows and Doors) is not a popover, but exhibits the same behaviour.
I neglected to mention that this only happens on my iPhone 6s Plus. On my iPad mini everything looks fine.
I tried this just now — copy/pasted button bar into a new file, then opened it in FileMaker Go 16 on my iPhone 6s Plus. Same result. I've attached the new file with just this button bar.
ButtonBarTest.fmp12.zip 69.2 K
Also how center/center spacing looks when I opened this file with FM Go 16 on iPhone 6 running iOS 10.3.3.
We're not able to replicate the reported problem.
I appears fine on my iPad and iPhone.
Based on some of the rendering of the lines between th segments ( and the variation of the width ), I would try adjusting the height a bit, to a number that result in each segment being in a full pixel range. For example, 14 segments x 24 pixels = 336 pixel total height. I can't recall right now if you need to adjust for the width of the line between segments. But making each segment be within a full pixel height will help the rendering.
Has anyone else tried an iPhone 6 Plus to see if that's where the problem lies (in the bigger iPhone screen somehow)?
Thank you for your posts, screen shots, and file.
Although I cannot replicate the issue on my devices, there is enough information in this entire forum thread to send to Development and Testing for review. When I receive any feedback, I will let you know.
1 of 1 people found this helpful
I'm seeing something similar in Go 16.0.2 on an iPhone 7 Plus. It occurs when the toolbars are shown or hidden.
The button bar border is set to 2pt and the dividers set to 1pt which makes it display as 2pt on Go 16.0.2 on iPhone 7 Plus.
In Go 16.0.2 on iPhone 7 Plus, the labels are top aligned and the dividers are double the thickness:
I've tried changing the height of the button bar to account for the 2pt border and 1pt dividers as follows:.
Original height: 150pts
Resized to account for 2pt border: 154pts
Resized to account for 1pt divider: 156pts
Resized to account for doubling up of 1pt divider (1pt divider displays as 2pts on iOS): 158pts
After every attempt, the top alignment persists.
The button bar is completely styled and the style is saved in the theme.
The same button bar in Go 16.0.2 on iPad:
Notice how the dividers are styled as they look on the Mac at 1pt.
I've tried removing the dividers and the top alignment persists.
1 of 1 people found this helpful
I've removed both the border and the dividers and resized the button bar to a height of 150pts and the text alignment is now honoured on the iPhone 7 Plus:
Adding the border back and keeping the button bar's height at 150pts, pushes the text alignment back to the top:
Notice the very thin white line between buttons 2 and 3.
Setting the button bar to a height of 152pts to account for the 2 point border keeps the text alignment at the top.
Setting the button bar to a height of 154pts sets the text alignment to the centre:
Adding a 1pt divider keeps the text aligned to the centre but displays the divider as if it's 2pts (which is how I want it to look but displays as 1pt on the iPad - see last screenshot in my previous post):
Changing the button bar height to 156pts and 158pts then pushes the text alignment back to the top:
Changing the button bar height to 160pts vertically centres the text and displays the divider as 2pts on both the iPhone 7 Plus and iPad Air, giving consistency across iOS, but different from the Mac (not a problem as I have device-specific layouts):
That looks very similar to some issues I remember running into with portals ( at the time it was in both Go and Pro ). Seems like the rendering engine needs a bit of tweaking to account for those additional heights.