Re: removeFrameUsingName: doesn't?
Re: removeFrameUsingName: doesn't?
- Subject: Re: removeFrameUsingName: doesn't?
- From: Quincey Morris <email@hidden>
- Date: Thu, 28 Feb 2008 13:22:25 -0800
On Feb 28, 2008, at 12:25, Mike Fischer wrote:
OK, nobody answered so I did a further test:
...
Then I relaunched the app, used the IBAction to remove the Auto Save
Name and quit the app again. The key was still there! So it's a bug
in AppKit/Cocoa it seems. NSWindow -removeFrameUsingName: does
nothing at all AFAICT.
Well this time I got interested enough to go read the NSWindow class
reference for removeFrameUsingName. It doesn't say that this method is
supposed to remove the key from the preferences. It *seems* to say
that it leaves the key but removes the frame data (in the sense of
setObject: @"" forKey: windowAutosaveName, it looks like, but I'm
guessing).
You didn't say whether you saw any non-blank saved frame data
associated with the key after using removeFrameUsingName.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden