Re: passing argument 1 of 'setContents:' from incompatible pointer type
Re: passing argument 1 of 'setContents:' from incompatible pointer type
- Subject: Re: passing argument 1 of 'setContents:' from incompatible pointer type
- From: Ken Ferry <email@hidden>
- Date: Sun, 8 Feb 2009 23:20:15 -0800
On Sun, Feb 8, 2009 at 9:39 PM, Michael Ash <email@hidden> wrote:
> On 2/8/09, Stephen J. Butler <email@hidden> wrote:
> > One thing to watch out for -- and it's generated some traffic on this
> > list recently -- is that NSImage creates hidden windows to manage
> > resources. So if you're loading many, many, many images, NSImage can
> > lockup the Window Server.
>
> This really needs a qualifier: NSImage *can* create hidden windows to
> manage resources. To be more specific, NSImage can create an
> NSCachedImageRep, which in turn creates NSWindows. The specific
> circumstances in which this happens are when you draw into an NSImage
> using lockFocus and the like, and at least sometimes when you draw
> with the image. Simply creating an NSImage from a file and then
> extracting one of its representations shouldn't create an
> NSCachedImageRep.
Drawing an NSImage that is backed by NSBitmapImageRep(s) will also never end
up creating windows on 10.5, and probably earlier.
-[NSImage lockFocus] is the main thing that will get the windowserver
involved.
The 10.6 AppKit release notes will have more on this topic[1].
-Ken
Cocoa Frameworks
[1] already do, for those who can read them.
_______________________________________________
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