• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
setFrameUsingName and (auto resizing) palette windows
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

setFrameUsingName and (auto resizing) palette windows


  • Subject: setFrameUsingName and (auto resizing) palette windows
  • From: Ron Aldrich <email@hidden>
  • Date: Tue, 20 Mar 2007 18:57:47 -0700

Folks,

I'm having a bit of a problem with a palette window in my application, who's size changes depending on it's content (The window doesn't have a zoom or resize control).

I'm saving the window's current frame in preferences, using setFrameAutosaveName, and I'm restoring it when the application launches using setFrameUsingName.

Everything works as expected, unless the window's size when the application quits is different from it's size in the .nib file.

In that case, when the application is re-opened, the window positions itself at the bottom left of its old frame, rather than at the top left, as would be expected.

Then, when the user opens a document, and the palette is resized to reflect the selected content, it now has effectively been moved from it's old position, downward by the height of the new content.

Does anyone have any suggestions as to how I should fix this?

Thanks,

Ron Aldrich
Software Architects, Inc.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


  • Prev by Date: NSImage lockFocus throws exception?
  • Next by Date: Re: Source List / + / - / Gear
  • Previous by thread: Re: NSImage lockFocus throws exception?
  • Next by thread: Weird (fatal) CoreData caching behavior
  • Index(es):
    • Date
    • Thread