Re: orderFront: 10.10 vs 10.9

2015-05-08 Thread Kyle Sluder
On Fri, May 8, 2015, at 09:40 AM, sqwarqDev wrote: > Can't help with the "why", but try putting > > [button lockFocus]; > > in that method. Even when there isn't an explicit unlockFocus call, I've > had this error message a couple of times and adding an explicit lockFocus > cured it. Please don

Re: orderFront: 10.10 vs 10.9

2015-05-08 Thread Torsten Curdt
Seems like I found the culprit. The drawing code was throwing an exception for a font that couldn't be found. cheers, Torsten On Fri, May 8, 2015 at 4:40 PM, sqwarqDev wrote: > > > > On 10.9 I am seeing > > > > "unlockFocus called too many times. > > > > Can't help with the "why", but try put

Re: orderFront: 10.10 vs 10.9

2015-05-08 Thread sqwarqDev
> > On 10.9 I am seeing > > "unlockFocus called too many times. Can't help with the "why", but try putting [button lockFocus]; in that method. Even when there isn't an explicit unlockFocus call, I've had this error message a couple of times and adding an explicit lockFocus cured it. B

orderFront: 10.10 vs 10.9

2015-05-08 Thread Torsten Curdt
I am staring at this code and don't get why it works fine under 10.10 while under 10.9 it does not. NSScreen *screen = self.window.screen; NSWindow *overlay = [[NSWindow alloc] initWithContentRect:screen.frame styleMask:NSBorderlessWindowMask backing:NSBackingStoreBuffered