Databases
StackOverflow2013
Postsdbo
PODispelling the UIImage imageNamed: FUD
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODispelling the UIImage imageNamed: FUD
    primarykey
    data
    text
    <p>Edit Feb 2014: <strong>Note that this question dates from iOS 2.0!</strong> Image requirements and handling have moved on a lot since then. Retina makes images bigger and loading them slightly more complex. With the built in support for iPad and retina images, <strong>you should certainly use ImageNamed in your code</strong>.</p> <p>I see a lot of people saying <code>imageNamed</code> is bad but equal numbers of people saying the performance is good - especially when rendering <code>UITableView</code>s. See <a href="https://stackoverflow.com/questions/316236/uiimage-imagenamed-vs-uiimage-imagewithdata">this SO question</a> for example or <a href="http://iphonedevelopertips.com/memory-management/images-and-caching.html" rel="nofollow noreferrer">this article</a> on iPhoneDeveloperTips.com </p> <p><code>UIImage</code>'s <code>imageNamed</code> method used to leak so it was best avoided but has been fixed in recent releases. I'd like to understand the caching algorithm better in order to make a reasoned decision about where I can trust the system to cache my images and where I need to go the extra mile and do it myself. My current basic understanding is that it's a simple <code>NSMutableDictionary</code> of <code>UIImages</code> referenced by filename. It gets bigger and when memory runs out it gets a lot smaller.</p> <p>For example, does anyone know for sure that the image cache behind <code>imageNamed</code> does not respond to <code>didReceiveMemoryWarning</code>? It seems unlikely that Apple would not do this.</p> <p>If you have any insight into the caching algorithm, please post it here.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USRog
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm in suspense. :)
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. USKriem
    2. COme too. Seems like SO isn't so full of geniuses as I thought.
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. USRog
    3. COSeems like you've spent some time investigating this. Have you done any experimentation that would show any negative impact of UIImage imageNamed with the latest cocoa-touch version? Create an UITableView and add lots (many thousands) rows and see if the performance goes down when you show different image in every row. Maybe then people can comment on your findings.
      singulars
      1. PODispelling the UIImage imageNamed: FUD
      1. USstefanB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload