> On Jun 18, 2016, at 11:04 AM, Richard Charles wrote:
>
> So I think the takeaway is that draw calls operate within a graphic context.
> If the context you want and need is the current context then you are good to
> go.
Just to reiterate, if the context you want to draw to is not active you
> On Jun 11, 2016, at 7:43 AM, Richard Charles wrote:
>
> Before calling drawRect:, the system locks focus on the view. Each view has
> its own graphic context. When the focus is locked on a view, the view’s
> graphics context is active. When the focus is unlocked, the graphics context
> is n
Apple is carefully monitoring bugs for this, so file one.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On Jun 18, 2016, at 4:21 AM, Andreas Mayer wrote:
>
> The really bad thing is, some were keeping old windows in memory!
___
Coco
> On 18 Jun 2016, at 19:21, Andreas Mayer wrote:
>
>
> Block based observers do still leak though.
>
Not quite sure what you were asking in the mail as a whole but one question
about block based observers, are you sure your block doesn’t have a retain
cycle, possibly introduced by migration
I have just migrated a project to Swift 3 which worked surprisingly well for
the number of changes necessary.
After checking out the new memory graph (cool!) I noticed that I am leaking
notifications. Example:
NSConcreteNotification 0x102c28600 {name =
NSApplicationDidBecomeActiveNotif
