mysterious behavior of system font metrics

I am using some code (Java) that assumes it is OK to create a size 1 font and then scale-transform it to render other font sizes. I would not expect this to work with Yosemite system fonts, but most of the time it works better than expected. But sometimes it does not. (The expected problem is

Re: Updated View Bounds After Orientation Change...

David and Ken, Thanks. What I needed was right @13:48 of the second video!!! > On Oct 27, 2015, at 1:50 PM, David Duncan wrote: > > In general I would highly recommend spending some time with this years Auto > Layout talks from WWDC. One of the many gems is the

Re: mysterious behavior of system font metrics

> On Oct 28, 2015, at 12:17 PM, Alan Snyder > wrote: > > The mysterious behavior that I observe is that the result of [NSFont > systemFontOfSize:1] can change over time. For example: The only guess I have is that it might depend on the scaling of the graphics

Re: mysterious behavior of system font metrics

On Oct 28, 2015, at 12:17 , Alan Snyder wrote: > > The mysterious behavior that I observe is that the result of [NSFont > systemFontOfSize:1] can change over time. For example: > > 2015-10-28 10:22:15.033 java[19620:15284886] >

Re: mysterious behavior of system font metrics

The log is showing the NSFont description: NSLog(@"%@", [NSFont systemFontOfSize:1]); No drawing was performed until after these log messages were written. There was no graphics context. In fact, no text was drawn using Core Text at all. Java does not use Core Text to draw text, but it does

Re: mysterious behavior of system font metrics

Thanks for the pointer. I will post there. Alan > On Oct 28, 2015, at 1:48 PM, Jens Alfke wrote: > > I believe there’s a mailing list on lists.apple.com > for CoreText; that might be a good place to ask. >

Re: NSFileWrapper - is this really so bad?

Perhaps just a little too OCD; however, if one is sending a message like count to a large number of containers using nil (Null) can be considerably more efficient then passing an empty shared instance. The Objective-C pattern when sending a message to a nil object pointer avoids the overhead of

Re: How to completely destroy/close a Window

Hi Ken, > No, this isn't relevant. When a window is controlled by a window controller, > releasedWhenClosed has no effect. See the docs. Ahhh, thanks. >> I have a NSWindowController and NSWindow Pair and I just want them both >> disposed of and re-created next time. > > > Dave, if you