• 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
Re: How a window was closed?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How a window was closed?


  • Subject: Re: How a window was closed?
  • From: Greg Guerin <email@hidden>
  • Date: Fri, 5 Mar 2010 10:33:04 -0700

Eric Gorr wrote:

The use of a global was considered and rejected. But, would likely be reconsidered if -windowShouldClose: does not work as expected.


Then add a category method that means "close but preserve open state for next launch", and call that from the termination delegate.

Or a category method that tells the receiver to copy its current open state, which will then be written to disk when the next close message is received.

I don't see a big difference in how the two things (user-close vs. close-but-preserve-opened-state) are distinguished by the panels. Use whatever makes sense for the code base. The key point is that the latter only occurs at app termination. Tying it into app termination is what makes it different.

  -- GG


_______________________________________________

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


  • Follow-Ups:
    • Re: How a window was closed?
      • From: Eric Gorr <email@hidden>
  • Prev by Date: Custom View in Toolbar
  • Next by Date: Re: Why CGPathAddCurveToPoint returns to the origin?
  • Previous by thread: Re: How a window was closed?
  • Next by thread: Re: How a window was closed?
  • Index(es):
    • Date
    • Thread