when placing some field on a layout, FileMaker places those object sometimes at 234.123 pt. Please place the objects at 234pt, not fractual...
Not sure if this rather belongs to Issue Reports since it's so obvious we don't want fraction values per default.
for me, it's an issue - but I'll guess that somebody will ask me to file a feature request when I file an issue report...
Indeed it´s a nightmare
AFAIK this report was never answered by FMI :
Aligning objects gives fractional points to position
I strongly disagree that fractional point positions are something we don't want. Between print output and retina displays, we're definitely rendering at a finer resolution than 1 pt, so I want control of that resolution, and I want FileMaker's feature to operate at that resolution by default. I think a better solution would be to allow multiple snap-to grids to be active at once, then developers can snap to a 1-point grid without switching away from whatever other grid they want to work with.
As far as I get this, it's not about to skip the ability of positioning objects by fraction of pixels via the inspector, but that when dragging a field onto layout, it should be positioned on even pixel coordinates per default, - kind of automatically snap to a 1-pixel grid at first.
when it comes to object placement, I don't care if there are retina-/whatever displays - I just wan't FM to place object in a way that doesn't make it harder than necessary for working.. The new method with the 'field picker' isn't a solution in every case.
jbante have valid point BUT : The major issue is when FileMaker cannot render object properly if placed in a fractional position, except when the "screen" support it. Then the object appear fuzzy / dirty
Moreover, FileMaker is not so coherent here, since i have seen cases on Windows plateform where high resolution screen are not properly supported : see the buttons of the toolbar as an example on a 4K screen connected on a windows computer.
And i dont talk about Windows system level scaling.
This "bug" is a part of more complex issue, where one have to accomplish a lot of extra efforts, very time consuming, when designing layouts because "sometimes" FM wont do a perfect job.
but of course if you are working in cm...
Set up the grid and snap to grid. That is the purpose of it. It prevents fractional dropping of objects. But overall, Those fractional placements are at times very much needed. I really do like the way it's implemented now. It gives us the power to do it either way without imposing a restriction.
Retrieving data ...