On 17 Jul 2014, at 4:01 am, edward taffel wrote:
> some of you may recall a previous thread of mine: ‘showing load progress for
> autosaved documents’; this is a recast version.
>
> from what i can discern, in the base case, application windows do not show
> until autosaved documents have loa
On 14 Jul 2014, at 19:41, Sean McBride wrote:
> On Mon, 14 Jul 2014 09:11:58 -0700, Jens Alfke said:
>> But I agree about NSNumbers being more complicated. The only time you
>> need to use an NSNumber is if you want to stick a number into a
>> collection or otherwise need to treat it as an object.
On Jul 17, 2014, at 6:35 AM, Graham Cox wrote:
>
> On 17 Jul 2014, at 4:01 am, edward taffel wrote:
>
>> some of you may recall a previous thread of mine: ‘showing load progress for
>> autosaved documents’; this is a recast version.
>>
>> from what i can discern, in the base case, applicati
I think there is a limit of 20 iBeacons that you could range for. Android can
see them all but iPhone limits you.
-Original Message-
From: cocoa-dev-bounces+jim.adams=sas@lists.apple.com
[mailto:cocoa-dev-bounces+jim.adams=sas@lists.apple.com] On Behalf Of David
Hoerl
Sent: Wedn
On 17 Jul 2014, at 11:34 pm, edward taffel wrote:
> (have you actually gotten similar to work?)
>
Yes, the scheme I've outlined is exactly how it works in my own app. I would
share the code with you, but it's not my IP to give away unfortunately. But
here's its description:
I have two cont
Every once in a while I run into a bug in my code that’s triggered by self
getting dealloced in the middle of a method. It’s usually something like
- (void) someMethod {
doSomeStuff;
[self.delegate object: self didSomeStuff: yeah];
doSomeMore
On Jul 17, 2014, at 20:01 , Jens Alfke wrote:
> The only thing I’ve found that works is
> CFRetain((__bridge CFTypeRef)self);
> at the top of the method, and a corresponding CFRelease at the end, but this
> is pretty ugly
This seems to be the right way to do it. A CFBridgingRetain/CFBridg
Using the objc_precise_lifetime attribute ensures the object stays alice to the
end of the block.
I think that's a bit better than abusing retain release.
> On 18 Jul, 2014, at 11:23, Quincey Morris
> wrote:
>
>> On Jul 17, 2014, at 20:01 , Jens Alfke wrote:
>>
>> The only thing I’ve foun
On Jul 17, 2014, at 8:40 PM, Roland King wrote:
> Using the objc_precise_lifetime attribute ensures the object stays alice to
> the end of the block.
>
> I think that's a bit better than abusing retain release.
I'm not sure if that is reliable. It's possible that the optimizer sees that
the
On Jul 17, 2014, at 11:01 PM, Jens Alfke wrote:
> Every once in a while I run into a bug in my code that’s triggered by self
> getting dealloced in the middle of a method. It’s usually something like
> - (void) someMethod {
> doSomeStuff;
> [self.delegate objec
On Jul 17, 2014, at 11:01 PM, Jens Alfke wrote:
> Once I’ve identified such a bug, the fix is easy: put a [[self retain]
> autorelease] at the top of the method. Except now I’m using ARC, and I can’t
> find a simple way of doing it. I tried adding
> __unused id retainedSelf = self;
> but t
Do you know this code will always run on the main thread? Because you could
fix this from the other side, in the delegate. Use
dispatch_async(dispatch_get_main_queue(), ...) to un-assign the property.
But this won't work if you're on a non-main thread when you call back into
the delegate.
On Thu,
12 matches
Mail list logo
