• 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: Should we release a CGImage created from NSBitmapImageRep ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should we release a CGImage created from NSBitmapImageRep ?


  • Subject: Re: Should we release a CGImage created from NSBitmapImageRep ?
  • From: Dave Keck <email@hidden>
  • Date: Sun, 6 Sep 2009 01:25:32 -1000

>From the docs on -CGImage

    "Returns an autoreleased CGImage object (an opaque type) from the
receiver’s current bitmap data."

... if you expect it to stick around, you need to retain it.
Otherwise, you needn't do anything: you shouldn't CGImageRelease() it,
because you don't own it.
_______________________________________________

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

References: 
 >Should we release a CGImage created from NSBitmapImageRep ? (From: DairyKnight <email@hidden>)

  • Prev by Date: Should we release a CGImage created from NSBitmapImageRep ?
  • Next by Date: Re: Code Signing
  • Previous by thread: Should we release a CGImage created from NSBitmapImageRep ?
  • Next by thread: Re: Should we release a CGImage created from NSBitmapImageRep ?
  • Index(es):
    • Date
    • Thread