On Nov 17, 2014, at 8:25 PM, Daniel Blakemore wrote:
>
> 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.
Look at your logs in Yosemite and see how many of these *Finder.app*
i
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 thin
> On 18 Nov 2014, at 1:50 pm, Roland King 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
>
>
> 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
> On 18 Nov 2014, at 1:33 pm, Roland King wrote:
> Try breakpointing on CGPostError - that used to work although I don’t recall
> whether it was iOS only or OSX as well.
>
> Chances it’s your bug are about 1%, that message has been popping up for
> years as various bits of iOS and OSX are br
> On 18 Nov 2014, at 10:19 am, Graham Cox wrote:
>
> When my app enters the Versions Browser, I get a stream of warnings logged
> like this:
>
> Nov 18 13:12:28 Grahams-iMac.local x[23685] :
> CGContextClipToRects: invalid context 0x0. This is a serious error. This
> application, or a li
When my app enters the Versions Browser, I get a stream of warnings logged like
this:
Nov 18 13:12:28 Grahams-iMac.local x[23685] : CGContextClipToRects:
invalid context 0x0. This is a serious error. This application, or a library it
uses, is using an invalid context and is thereby contrib
In Xcode 6.1.1, it seems that the UILongPressGestureRecognizer doesn't work
quite right.
I have an lpgr in my storyboard set for 3 seconds, 1 touch, 0 taps. If I click
with the mouse in the Simulator and just hold it, my action is not called until
I either move the mouse or release the button,
Hi Gideon,
While at first glance this looks horrendous, it does seem to be stuck in a
low-level image rasterizing operation, and the call stack suggests it's in a
sublayer. So it is pointing to your layer-hosting subview as the culprit. When
scrolling or zooming "normally" it might be able to a
I hope they haven¹t gone to layer backed views for text. If you have a
choice turn that off. We have a teleprompter app which scales formatted text
nicely on Mac, but was found to be unusable on iOS due to layer backing.
On 11/17/14 3:00 PM, "cocoa-dev-requ...@lists.apple.com"
wrote:
> Hi, I ha
On Nov 17, 2014, at 9:52 AM, Sean McBride wrote:
> Seems they did not understand I was looking for a workaround, which I have
> now reiterated.
Let us know if you find a workaround.
Richard Charles
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple
On Sat, 15 Nov 2014 14:02:44 -0500, Jerry Krinock said:
>
>> On 2014 Nov 15, at 13:38, Fritz Anderson wrote:
>
>> rdar://18994451; I classified it as a data-loss bug, given the near-
>certainty of the loss of the journal files.
>
>Indeed it is, Fritz, for the reasons you stated.
>
>Here was my ve
Hi, I have an app where I need to programmatically scroll the content of a full
screen scroll view.
I have always done this using scrollPoint on my view. I have been using this
since 10.6. My view is not layer backed and has a single subview which is a
layer *hosting* view.
Now in Yosemite 10.
13 matches
Mail list logo
