Re: New CGContext warning in Yosemite
Re: New CGContext warning in Yosemite
- Subject: Re: New CGContext warning in Yosemite
- From: Daniel Blakemore <email@hidden>
- Date: Mon, 17 Nov 2014 20:25:17 -0700
I realize this is not a foolproof solution and is more of a breadcrumb, but
I remember finally getting tired of getting spammed with these on an iOS
app I was developing and hunting them down. It has something to do with a
view trying to draw with zero frame or something along those lines.
I think they print the message because they want to be able to say they
told you so when your app starts crashing otherwise without warning on some
version update.
I had the same kneejerk as you when I first got the error, but I've come to
ignore them like the constraint logs that print out when your view is
initialized with a zero frame: until they make it hard to see useful logs.
Roland seems to feel the same way.
At the end of the day, though, your issue appears to be entirely contained
within Apple code, so I'd ignore them and chalk it up to another slight
lapse in QC recently.
--
Daniel Blakemore
Pixio Software
On Mon, Nov 17, 2014 at 8:11 PM, Graham Cox <email@hidden> wrote:
>
> > On 18 Nov 2014, at 1:50 pm, Roland King <email@hidden> wrote:
> >
> >>
> >>
> >> Which suggests you're right, it's not my bug. You'd think Apple would
> deal with these before a major OS release.
> >>
> >
> > Ha ha. I feel Apple have adopted the same relaxed attitude to that
> 'courtesy notice’ as I have. They did fix one during the iOS6 betas, which
> was good as it came up just about every time you used a non-English
> keyboard and was very annoying.
> >
>
>
> Yep, it's very annoying. It's either serious, in which case it should be
> fixed, or it's not serious, in which case they should change the wording of
> the message to say so. Especially as I suspect every CGxxx function starts
> with the preamble:
>
> if( context == NULL )
> {
> LogPanickyWarningMessage();
> return;
> }
>
> ... continue ...
>
> In other words if it does get a nil context, it does nothing, so whatever
> call stack led to that point just unwinds without drawing anything. That's
> fine, but what's the BS about "contributing to an overall degradation of
> system stability and reliability"?
>
> --Graham
>
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden