Looks like the cavalry has arrived to the south.
Alex, do we have 44-40 ammunition for the gentlemans?
We are just holding Miller`s Bridge!!!.
@ Jonathan:
>There is a problem with Hans' solution. It fits the boxes tightly around the
fonts as measured at runtime. This makes it impossible for a user to know
if the same patch with a different font will have overlapping objects on another user's machine.
If is impossible to know what happens on a different font why don’t we stick to “one” for a standard.
>(Or the same font with a different font-rendering stack, or even
a different version of the same stack!)
I trust in you but this is out of scope for me.
How this translate on using just one “font” on just one “vanilla”?
Mensaje telepatico asistido por maquinas.
From: Pd-list <pd-list-bounces@lists.iem.at> on behalf of Dan Wilcox <danomatika@gmail.com>
Sent: Sunday, February 12, 2017 7:45 AM
To: Jonathan Wilkes
Cc: Pd-List
Subject: Re: [PD] cross platforms issues with displaying fonts in vanilla but not in Purr Data
Good to know the reasoning why the pixel fiddling stuff didn’t make it over with the guy update into vanilla.
I’m seeing the padding issue with the object boxes when rendered in high dpi on OSX and now I know what it is.
I do agree with Alexandre that using the same font on all platforms would help in regards to layout in patches between OSs.
For some fonts/font sizes the best fit will inevitably leave some extra space at the
right of the box inside the border. But that space is visually required to keep
users from placing two boxes so close together that they overlap on a platform
that renders the same font slightly wider.
Otherwise you get users caught up in a vicious cycle of breaking/fixing each
other's object spacing in patches.