Databases
StackOverflow2013
Postsdbo
POUITableView is slow
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUITableView is slow
    primarykey
    data
    text
    <p>I have a <code>view</code> which I dragged a <code>UITableView</code> in it, and 2 <code>UIImageView</code>s (the 1st one to show a background image and the second one is just showing a very small title at the top of the view with an image). They're all set to <code>weak</code> properties. The tableView has 495 rows and an image loads into each cell. Here's the code for configuring a cell:</p> <pre><code>- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath { static NSString *CellIdentifier = @"Cell"; UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier]; if (cell == nil) { cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier]; } int cellNumber = indexPath.row + 1; NSString *cellImage1 = [NSString stringWithFormat:@"c%i.png", cellNumber]; UIImage *theImage = [UIImage imageNamed:cellImage1]; [cell.imageView setImage:theImage]; UIView *bgColorView = [[UIView alloc] init]; [bgColorView setBackgroundColor:[UIColor brownColor]]; [cell setSelectedBackgroundView:bgColorView]; return cell; } </code></pre> <p>I use <code>segue</code>s, so I don't need the delegate method. (which not relevant to this question either). The thing is, the scrolling is smooth; BUT if I scroll <em>TOO FAST</em> then it gets slow and probably causes the app to crash. The png images loaded into cells are not big sizes, each one is around 5KB. It seems the the dequeueing job is not done efficiently; cuz it gets slow, shows a memory warning message and then the crash happens. Anything I can do about it? (there's nothing else in the view) </p> <p>UPDATE: I've also tried removing this part of code:</p> <pre><code>UIView *bgColorView = [[UIView alloc] init]; [bgColorView setBackgroundColor:[UIColor brownColor]]; [cell setSelectedBackgroundView:bgColorView]; </code></pre> <p>no use!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMilad
    1. USMilad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUITableView is slow
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUITableView is slow
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUITableView is slow
      1. USCallmeed
      1. VTFavorite
    1. CO// the fast scrolling doesn't make iPod app slow! and it has both texts and images in it either. and this only happens on the device. Of course with the simulator, there's not a single problem and it's VERY smooth.
      singulars
      1. POUITableView is slow
      1. USMilad
    2. COHave you considered moving the bgColorView creation logic into `if (cell = nil)` block? Otherwise, you're going to be creating that view every single time a cell is to be displayed...
      singulars
      1. POUITableView is slow
      1. USDPlusV
    3. COI have even removed that part. it's still the same.
      singulars
      1. POUITableView is slow
      1. USMilad
 

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