in the Portland, Oregon Metropolitan
Area.
On Wed, May 6, 2015 at 2:25 PM, Aaron Montgomery
eey...@monsterworks.com wrote:
Having cycler set to assign and then releasing it in dealloc doesn't feel
right. Why not set cycler to retain, add an autorelease in init then
release _cycler in dealloc
Works for me. Not saying it doesn't work for you, but the problem isn't the
code.
Created a fresh Single View Application iOS project.
Replaced ViewController.m source with the code below.
Added a UITableView to the View Controller's View and hooked up the DataSource
to the View Controller.
Ran
On Sep 12, 2013, at 9:17 AM, Graham Cox graham@bigpond.com wrote:
On 12/09/2013, at 6:07 PM, Kyle Sluder k...@ksluder.com wrote:
Personally, I would avoid doing this, as it could cause reentrancy among
KVO observers of eventTypes. Instead, I'd assign to mEventTypes directly
from your
On Sep 12, 2013, at 2:45 PM, Peter Teeson ptee...@icloud.com wrote:
Xcode 4.6.2 Lion 10.7.5
Programming with Objective-C seems to indicate I can do this:
#import Cocoa/Cocoa.h
#import Cell.h //My sub-class
@interface Document : NSDocument
@property Cell *protoCell;
@end
and this
On Sep 12, 2013, at 3:02 PM, Lee Ann Rucker lruc...@vmware.com wrote:
On Sep 12, 2013, at 2:52 PM, Aaron Montgomery wrote:
I think it is either
_protoCell = [[Cell alloc] init];
or
self.protoCell = [[Cell alloc] init];
These aren't equivalent unless the @property is assign, which
I've been trying to reproduce this problem, but haven't been able to get the
warning on a minimal example. However, I noticed something unusual trying to
build a minimal example to play with. Here's a stripped down example (Xcode
4.6.3):
#import Foundation/Foundation.h
@interface MWObject :
Right, sorry, threw it together too quickly and have been living too long in
the land of ARC. Correcting the setter, fixing the dealloc method and removing
the newObject method (see below):
@interface MWObject : NSObject
@property (nonatomic, strong) NSObject* object;
@end
@implementation
Hi,
I'm currently running into this issue trying to use Telerik Test Studio (and am
asking about it there as well), but I think the issue is more general and would
like some ideas.
The situation: Test Studio drives my app's user interface from a background
thread. In some places where the
I use goto in places with ARC without too much trouble. When I get this
warning, it is because ARC cannot figure out the lifetime of an object created
after a possible branch and before the the . Sometimes you can get rid of the
error by simply making the lifetime clear. Here's a silly example
On Jan 24, 2013, at 6:46 PM, Chuck Soper chu...@veladg.com wrote:
On 1/24/13 6:30 PM, Quincey Morris quinceymor...@rivergatesoftware.com
wrote:
It's clearly documented that they're optional in your situation, and the
documentation is 10.7-vintage. The 10.8 SDK header file also says they're
It has been awhile since I last did a conversion, but I do remember that when I
Analyzed my project it didn't raise any issues, but when I tried to convert to
ARC there were a few places where these issues were raised that I needed to
fix. Also, converting to ARC might actually move the
11 matches
Mail list logo
