>From: Hans-Christoph Steiner <hans@at.or.at>
>To: Jonathan Wilkes <jancsika@yahoo.com>
>Cc: Miller Puckette <msp@ucsd.edu>; "pd-dev@iem.at" <pd-dev@iem.at>
>Sent: Tuesday, June 18, 2013 8:55 PM
>Subject: Re: [PD-dev] remove tk scaling

>On 06/18/2013 06:21 PM, Jonathan Wilkes wrote:
>>
>>
>>
>>
>> ________________________________
>>  >From: Miller Puckette <msp@ucsd.edu>
>>> To: Hans-Christoph Steiner <hans@at.or.at>
>>> Cc: pd-dev@iem.at
>>> Sent: Tuesday, June 18, 2013 2:12 PM
>>> Subject: Re: [PD-dev] remove tk scaling

[...]

>>> (the relevant doc is in the "font" manual age for TK; "If size is
>> a negative number, its absolute value is interpreted as  a  size in pixels."
>>
>> That's exactly what Pd does-- I should have said in my previous message
>> I tested patches with 0.44-3 on Debian Wheezy, OSX, and Windows
>> XP.  All the iemgui and object fonts must be negative because they are
>> pixel exact whether you use [tk scaling 0.2] or [tk scaling 8].
>>
>>Furthermore, if someone codes a gui external that doesn't use pixel
>> sizes for fonts to appear on the canvas _and_ they want pixel-exactness,
>> it's a bug, no?
>>
>> -Jonathan

>The situation is a big mess, no argument here.

No, it's not.  As I said, patches are currently pixel-exact across platforms,
and they remain that way regardless of the value supplied to [tk scaling].

>But you're not going to fix it
>by messing with [tk scaling], you'll just fix one issue, and others will pop
>up.

Can you give an example of one of those issues?

So far you have a single comment about pixel-exactness which is at the very
least no longer relevant.  (While there is a bug related to the default tk scaling
value, it's in a different domain and has evidently been solved with a one-liner,
without introducing the font problems I mentioned.)

-Jonathan