• 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
Why would a view be asked to draw after its window has been ordered out?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why would a view be asked to draw after its window has been ordered out?


  • Subject: Why would a view be asked to draw after its window has been ordered out?
  • From: James Walker <email@hidden>
  • Date: Thu, 13 Dec 2018 10:44:57 -0800

I was getting a crash on quit resulting from a drawRect: method being called on a window that had been ordered out. I can solve the immediate problem just by bailing out of drawRect: if the window is invisible, but I wish I understood what's going on. The call stack shows a run loop observer calling CA::Transaction::commit() resulting in -[NSWindow displayIfNeeded] being called, but I don't know why displayIfNeeded would do anything with an invisible window.
_______________________________________________

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: Why would a view be asked to draw after its window has been ordered out?
      • From: Matt Jacobson <email@hidden>
  • Prev by Date: Re: Custom NSButton image effects for pressed/disabled
  • Next by Date: Re: Why would a view be asked to draw after its window has been ordered out?
  • Previous by thread: Re: Custom NSButton image effects for pressed/disabled
  • Next by thread: Re: Why would a view be asked to draw after its window has been ordered out?
  • Index(es):
    • Date
    • Thread