On 31 Dec 2014, at 14:04, Charles Jenkins wrote:
> I have a non-retina Mac and no experience knowing what happens to graphics
> when used on a retina screen. I bought PixelCut's PaintCode as a Christmas
> present to myself so that my images could be made resolution-independent, but
> I'm having
On 01 Jan 2015, at 02:50, Jack Brindle wrote:
> You might want to extend that. The header file indicates that containsString:
> _only_ is available in OS X starting with 10.10 and iOS starting with 8.0. I
> would expect this to crash, or at least behave very poorly, under any prior
> OS since t
Duet adds a connected iPad as a second display which you can set to use Retina
resolution. I just tried it and it seems to work pretty well with only a slight
lag. I bought Duet with the main purpose of testing my apps at the Retina
resolution without having to switch the main display to one.
h
> On 1 Jan 2015, at 23:00, Uli Kusterer wrote:
>
> On 01 Jan 2015, at 02:50, Jack Brindle wrote:
>> You might want to extend that. The header file indicates that
>> containsString: _only_ is available in OS X starting with 10.10 and iOS
>> starting with 8.0. I would expect this to crash, or a
-- Forwarded message --
From: *SevenBits*
Date: Thursday, January 1, 2015
Subject: Application Crashing Under Mavericks, but not Yosemite
(Entitlements Issue?)
To: Uli Kusterer
On Thursday, January 1, 2015, Uli Kusterer > wrote:
> On 01 Jan 2015, at 02:50, Jack Brindle wrote:
On 01 Jan 2015, at 16:15, SevenBits wrote:
> Uli: is it possible to create a category which defines a method called
> containsString:, and only have it activate on 10.9 or lower and use the new
> Apple method on 10.10 and above?
In theory, you could add code on 10.8 and earlier that registers
Thank you all for that good information. :-)
I once had AirDisplay for my iPad, so I need to re-download it and see what I
need to do to get it going with Yosemite.
—
Charles Jenkins
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please d
Greetings, O readers of the sacred list !
Merry Xmas, and a Happy New Macintosh, btw.
On X.6 Snow Leopard, a QuickLook preview executed from the Finder is
displayed in a window with a translucent black background. The text color is
white, ergo.
On the same sy
> On Jan 1, 2015, at 1:25 PM, Eden Smallwood wrote:
>
> If you’re thinking "Wh on Bk and Bk on Wh, therefore XOR to the
> rescue", I’ve tried every conceivable setting of cgBlendMode and
> nsCompositingMode and nothing has any effect whatsoever on the text color
> which results in the w
On Jan 1, 2015, at 13:25 , Eden Smallwood wrote:
>
> How does Apple know to make the text white in one place and black in
> the other?
How are you choosing the color for your text? Have you tried [NSColor
textColor] or perhaps [NSColor controlTextColor]?
_
Hi all,
I know I'm very, very late to the party, but I'm building my first ever project
with ARC instead of manual retain/release (which I was always very comfortable
with). Frankly, I'm finding it frustrating because it seems much harder to know
how memory is managed. Anyway. I will plough on
> On Jan 1, 2015, at 3:38 PM, Graham Cox wrote:
>
> Hi all,
>
> I know I'm very, very late to the party, but I'm building my first ever
> project with ARC instead of manual retain/release (which I was always very
> comfortable with). Frankly, I'm finding it frustrating because it seems much
> On 2 Jan 2015, at 10:52 am, David Duncan wrote:
>
> The first thing to keep in mind is that unless otherwise qualified, all
> object references are owned - locals, ivars, array entries, etc. The places
> where this isn’t possible (such as structs) are flagged as compiler errors.
> The lifet
On Jan 1, 2015, at 17:20 , Graham Cox wrote:
>
> I'm using Allocations, but I'm finding the volume of data a bit overwhelming.
>
> As an aside, Leaks shows nothing at all. Does that mean I'm not actually
> leaking anything?
Forget Leaks, it’s an utter waste of time*. Use marked generations
A while back I had a similar sounding issue in an iOS project I was working on.
The memory usage kept growing, although I could find no obvious culprits in my
code after hours of exploration. My solution probably doesn’t pertain to you,
but I thought I’d pass it along just in case it’s something
+1 for all of this. I wouldn't call leaks an utter waste of time, but it really
does only find pure retain cycles (which it then annotates very nicely) and not
memory which is really is pinned by a real reference which is more often the
case. Also, if you're using KVO anywhere, this tends to ent
> On 2 Jan 2015, at 12:48 pm, Quincey Morris
> wrote:
>
> That usually means the block and the ‘self’ it captured mutually refer
> to each other. I’m betting this is what’s wrong in your case.
>
>
Quincey, thanks for your lengthy and well-thought-out reply (as usual) :)
I think you'v
>
> My handler block refers to 'self' quite extensively - it calls other methods
> of self and also refers to properties such as self.delegate. I'm not quite
> sure how I can rework it not to refer to self. Maybe I just need to not use
> the completion block approach and use a delegate callbac
> On 1 jan 2015, at 18:26, Graham Cox wrote:
>
>
>> On 2 Jan 2015, at 12:48 pm, Quincey Morris
>> wrote:
>>
>> That usually means the block and the ‘self’ it captured mutually refer
>> to each other. I’m betting this is what’s wrong in your case.
>>
>>
>
>
> Quincey, thanks for you
> On 1 jan 2015, at 18:22, Roland King wrote:
>
> +1 for all of this. I wouldn't call leaks an utter waste of time, but it
> really does only find pure retain cycles (which it then annotates very
> nicely) and not memory which is really is pinned by a real reference which is
> more often the
> On 2 Jan 2015, at 10:52, Joar Wingfors wrote:
>
>
>> On 1 jan 2015, at 18:22, Roland King wrote:
>>
>> +1 for all of this. I wouldn't call leaks an utter waste of time, but it
>> really does only find pure retain cycles (which it then annotates very
>> nicely) and not memory which is real
> On Jan 1, 2015, at 18:26, Graham Cox wrote:
>
>
>> On 2 Jan 2015, at 12:48 pm, Quincey Morris
>> wrote:
>>
>> That usually means the block and the ‘self’ it captured mutually refer
>> to each other. I’m betting this is what’s wrong in your case.
>>
>>
>
>
> Quincey, thanks for yo
> On 2 Jan 2015, at 1:46 pm, Roland King wrote:
>
> Having a handler block which refers to self is not in and of itself a
> problem, very many blocks implicitly do. The block retains self, however in
> most cases something else retains the block and the self reference goes away
> when the blo
23 matches
Mail list logo
