Doc Block posted:

Maybe NSNumberFormatter?

carry on then posted:

Are there any good guides (in the Apple documentation or otherwise) for creating GUI applications for OS X, especially with advice on how to structure the controllers, how to get controllers talking to each other, and other design patterns?

stray posted:

I've got this big dictionary in a plist of addresses, phone numbers, etc. I'm accessing it through a standard UINavigationController / UITableViewController setup, but there might be modes of the app where we want to open that data from whatever view we're in.

So essentially: how do I create a view controller that takes/requires a parameter to instantiate correctly?

Apple posted:

Typically in a dealloc method you should release object instance variables directly (rather than invoking a set accessor and passing nil as the parameter) ... If you are using the modern runtime and synthesizing the instance variable, however, you cannot access the instance variable directly, so you must invoke the accessor method

pokeyman posted:

1. Is there any point to niling out instance variables after releasing them?

quote:

2. Can I use accessors (e.g. self.something = nil) instead of releasing directly?

lord funk posted:

Is Xcode 4.1 more stable than 4.0.2? I've been sitting at 4.0.1 for a while and I'm reluctant to upgrade (for no reason other than preventing headaches), but it is crashing constantly.

rjmccall posted:

Please file a bug against the documentation; that's old information.

quote:

dealloc words

lord funk posted:

Because I'm getting that about 60% of the time I hit run. Full on hang, force quit, reopen, clean, build, run. And this is after insignificant or no changes to the code.

lord funk posted:

I have 4 gigs of RAM.

I turned the GDB debugger off - that has stopped the problem. I don't have a debugger, but at least I can work a little more today. Tomorrow I'll reinstall Xcode.

Ender.uNF posted:

Do not examine retainCount or pay any attention to it whatsoever. It is the most dangerous form of madness, guaranteed to lead you down the path of destruction.

When an object is being deallocated, what is the point of maintaining retainCount?
Answer: Nothing! by definition, touching a reference after it is deallocated is an invalid operation. Therefore by definition any ivar can return any and all possible values because you are touching memory you promised not to touch. It is no different than saying MyObj *o = (MyObj*)(void*)0x82498384; What is at that memory address? who knows! If you're lucky you'll get an immediate crash.


Second, [[Partner alloc] retain] is not a valid initialized object because you never called init. An alloc'd object is already retained automatically. You should be calling [[Partner alloc] init]. So again, by definition, you can have *any* behavior because you are doing stuff that makes no sense.

Further, a +create method like that should be returning the object autoreleased, so you should be doing [[Partner alloc] init] autorelease]. Then the code that receives the object should retain it if it needs to (placing an object in an array retains it).


You have some serious memory management issues going on and I would suggest reviewing the memory guide, running the Analyze option in Xcode, run the Leaks Instrument, then run with malloc debugging enabled. That should help you track down your memory management issues.

Sir Davey posted:

Thank for the help! I reread the documentation and now I understand it better.

HOWEVER, I was not wrong to wonder wtf was happening when the object was being deallocated even though the retainCount was far greater than 1! It turns out, I had this bit of code in the Favoritable class, which is inherited by Partner:

code:

-(void)release{
        [super dealloc];
	Name = nil;
	ShortDescription = nil;
	Icon = nil;
	[super release];
}

What the gently caress was I thinking when I put a dealloc in the release function? Who knows, but now I know it was a stupid as poo poo mistake and I won't ever, ever, ever do this poo poo again.

Spelter posted:

you shouldn't be doing anything like setting Name, ShortDescription and Icon properties to nil

Eggplant posted:

I am using an older (2007) MBP, not planning to upgrade to Lion yet. I need to reinstall Xcode 4, but the app store only provides the lion-only 4.1 now. Is there a way to get a previous version?

lord funk posted:

As suggested in a WWDC video, I moved all my graphics calls to a background thread to prevent it from tying up the main thread. It's not a graphics heavy app, but I shaved 30ms off the response time for UITouch events. In the audio world that is huge!

A.S.H. posted:

So I am talking to my landlord, and he wants to make a calendar app, but not just any calendar app or I wouldn't be posting in here. It's a religious calendar, apparently he's in a community that's related to Russian Orthodox but part of an Old Worship Sect, something of that nature. The bottom line is he wants to provide his community with this App for religious observances, like on certain holiday's they aren't allowed to produce income, that sort of daily doctrine. The last offer he got from someone to make this App was $15,000 which sounds a little steep for a calendar. My landlord is going to photocopy the calendar for this year, and create a written outline of specific observances, I'm hoping that is sufficient data to get this off the ground. Please reply to this post or send me a PM if you are interested in taking on this project.

Small White Dragon posted:

I need to look through some serialized (NSKeyedArchived output) data. Any good tools for this?

Carthag posted:

From the docs it looks like it's a binary plist. Try writing it to a file with .plist extension and opening it in the Property List Editor.

http://developer.apple.com/library/...WithRootObject:

Small White Dragon posted:

I've opened it that way, and it's somewhat indecipherable

stray posted:

I've seen a number of people (not here) who insist that the only proper way to release something is by setting it to nil before releasing it, like so:

code:

- (void)dealloc {
	[foo release], foo = nil;
	[super dealloc];
}

Doc Block posted:

My opinion is that it's a waste of time. While trying to pass messages to nil might be "safe" in that it won't crash your program, it almost certainly will result in incorrect behavior.

carry on then posted:

carry on then posted:

Nothing ever happens. The checkbox is unchecked even when the BOOL is set to YES. None of the NSLog statements I put in the preferencesDidChange: method ever print, and the whole app just locks up. Trying to use breakpoints to see what happens is useless because as soon as closePreferences: in PreferencesController finishes, the debugger shows me all the assembly. No issues appear in Xcode and no errors print in the debugger.

quote:

I think the reason this isn't working is because I'm using a C# model for this. In that environment, I would just initialize the form and hand it a reference to the controlling class, then have the form tell that class when it was about to close and to get the data it needed, then close the form. I think the differences between C# (and Java, which I'm also more familiar with) and C/Objective-C are messing me up, but with no error messages, I'm at a loss as to what to do.

Doc Block posted:

I'm just an iOS dev, and still learning Cocoa myself, but I think you should look up key-value observing (KVO) and bindings, which were meant to help alleviate these kind of problems.

Read Cocoa Programming For Mac OS X. While somewhat out of date (2008) it's still a good introduction (and a new edition is supposedly coming in October). The author tries to get the reader to do things The Cocoa Way, which is important if you're coming from another language.

NoDamage posted:

Breakpoint in your PreferencesController's awakeFromNib and see if funBox is nil when you're calling setState on it. (This is one adjustment you need to make coming from other languages, calling a method on a nil variable simply does nothing, instead of crashing or showing an error.)