• 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: +{NSImage imageNamed:fromBundle:]?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: +{NSImage imageNamed:fromBundle:]?


  • Subject: Re: +{NSImage imageNamed:fromBundle:]?
  • From: Ricky Sharp <email@hidden>
  • Date: Fri, 11 Jan 2008 15:34:23 -0600


On Jan 11, 2008, at 2:10 PM, glenn andreas wrote:

NSImage's +imageNamed: is documented as searching the named images cache, the apps main bundle, and then the AppKit framework bundle. Unfortunately, I've got code in a private framework that wants to get the image stored that framework (which isn't thus searched).

Is there some way to add a framework to this search path? (Which would be best, because it will allow any object, such as a button, that has an image name to automatically work correctly) Or at least a way to explicitly pass a bundle to search (via a hypothetical +imageNamed:fromBundle:). The fall back, of course, is to get all the possible file extensions from NSImage and manually try each and every one of them, but I'd rather not have to duplicate this logic (plus this fails to support the generic button using a named image that resides in the private framework)...

As others have pointed out, use NSBundle's pathForImageResource. I created an image factory that knows how to scan multiple areas looking for images.


I suppose I could also, at startup, go through all the images in the framework, load them, and then do a "setName:" to get them in the cache (but this seems like it could impact program launch times)


Well, that may not be bad since load times are often very, very low. It's probably the case where image data is not decoded until you're actually drawing things.

For example, all my images are PDF (to support res-ind). While my factory loads them on-demand (and not all at once), I did measure the total loading time over the lifetime of the app. This was the time taken to actually alloc/init NSImage images and then call setName:.

When the images were then _drawn_, that's where the bulk of the time was taken. Maybe this is specific to PDF; I don't know. For PDF the raw data is loaded, but not "decoded" until drawn; also at the time of drawing, that's where you end up with cached reps (e.g. a cached bitmapimagerep) that will ultimately speed up drawing for the 2nd, etc. times the image is drawn.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

_______________________________________________

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: +{NSImage imageNamed:fromBundle:]?
      • From: glenn andreas <email@hidden>
References: 
 >+{NSImage imageNamed:fromBundle:]? (From: glenn andreas <email@hidden>)

  • Prev by Date: Re: NSTextfield value doesn't update binding when set programmatically
  • Next by Date: Re: core data subentities
  • Previous by thread: Re: +{NSImage imageNamed:fromBundle:]?
  • Next by thread: Re: +{NSImage imageNamed:fromBundle:]?
  • Index(es):
    • Date
    • Thread