• 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: showing window causes EXC_BAD_ACCESS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: showing window causes EXC_BAD_ACCESS


  • Subject: Re: showing window causes EXC_BAD_ACCESS
  • From: Daniel Child <email@hidden>
  • Date: Sat, 27 Sep 2008 13:06:30 -0400

No. But I'm still wondering. How would you set up a reference again if you chose to have the window released on close...without reloading the entire nib, which is probably counterproductive.

On Sep 26, 2008, at 3:30 PM, Charles Steinman wrote:

If it's accessed via an outlet in your app controller, you probably don't have multiple instances of it floating around like Scott was talking about, do you?

_______________________________________________

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: showing window causes EXC_BAD_ACCESS
      • From: Uli Kusterer <email@hidden>
    • Re: showing window causes EXC_BAD_ACCESS
      • From: "Kyle Sluder" <email@hidden>
References: 
 >Re: showing window causes EXC_BAD_ACCESS (From: Charles Steinman <email@hidden>)

  • Prev by Date: Re: window controllers and managed object contexts
  • Next by Date: Re: window controllers and managed object contexts
  • Previous by thread: Re: showing window causes EXC_BAD_ACCESS
  • Next by thread: Re: showing window causes EXC_BAD_ACCESS
  • Index(es):
    • Date
    • Thread