Re: setFrameUsingName , setFrameAutosaveName
Re: setFrameUsingName , setFrameAutosaveName
- Subject: Re: setFrameUsingName , setFrameAutosaveName
- From: Jeremy Dronfield <email@hidden>
- Date: Fri, 13 Sep 2002 19:08:32 +0100
On Friday, September 13, 2002, at 04:54 am, Tony S. Wu wrote:
I just can't figure out why it doesn't work in my real application.
But it's ok, I'll just save the frame manually.
That might not be such a great idea. If these methods aren't working,
there's probably some root problem which could cause trouble elsewhere.
Here are my suggestions (sorry if they seem insulting, but these
problems nearly always turn out to be caused by something incredibly
simple).
- Have you accidentally deleted your bundle identifier in the targets
window? This would cause your app to start saving defaults into a file
called (YourApplicationName).plist.
- Are you using PLE to look at your prefs file? If so, are you properly
quitting the app and re-opening the plist file before checking whether
the new value is there?
- Are you sure you're entering this code into a file that gets included
in your built app? I know it sounds stupid, but moving files around can
result in more than one version of a source file being entered in that
popup menu above PB's editor. I've caught myself typing code into a
defunct source file as a result of relying exclusively on that popup for
navigation.
-Jeremy
========================================
email@hidden // email@hidden
The Alchemy Pages:
- fractious fiction at
http://freespace.virgin.net/jeremy.dronfield
========================================
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.