> On 3 Mar 2015, at 11:42 am, Uli Kusterer wrote:
>
> Sounds like an actual bug, at least I don’t get this behaviour in my popvers.
> Are you sure your NSPopover is still valid at the point? What does calling
> malloc_size() on the pointer return? If it’s 0, it’s already been disposed.
I'm no
On Mar 2, 2015, at 4:14 PM, Graham Cox wrote:
> I'm getting an exception thrown by the NSPopover code when a popover is going
> away. Due to the way popovers are handled, the exception is not one I'm able
> to catch, so the app is terminated. This is a very big punishment for what
> seems a tr
On 03 Mar 2015, at 00:14, Graham Cox wrote:
> I'm getting an exception thrown by the NSPopover code when a popover is going
> away. Due to the way popovers are handled, the exception is not one I'm able
> to catch, so the app is terminated. This is a very big punishment for what
> seems a trivi
I'm getting an exception thrown by the NSPopover code when a popover is going
away. Due to the way popovers are handled, the exception is not one I'm able to
catch, so the app is terminated. This is a very big punishment for what seems a
trivial transgression that doesn't even matter at this tim
