• 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
Profound UITableView rendering-performance problem, but only at certain positions? mostly resolved
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Profound UITableView rendering-performance problem, but only at certain positions? mostly resolved


  • Subject: Profound UITableView rendering-performance problem, but only at certain positions? mostly resolved
  • From: Gavin Stokes <email@hidden>
  • Date: Mon, 23 Jul 2012 01:18:12 -0700

I found that this only happened when 51 pixels or fewer of the last row of
a section were visible at the top of the screen. The row height returned
was 97.  So 51 was a baffling number, not being half the row height or of
any other significance I could see.

Turns out that the tableview specified a row height of 97 (in the XIB), but
the custom cells in it give themselves a height of 100 upon instantiation.
 Somehow this disparity triggered the problem.  Changing the row height to
100 in the XIB's UITableView definition eliminated the artifacts.
_______________________________________________

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: Profound UITableView rendering-performance problem, but only at certain positions? mostly resolved
      • From: Fritz Anderson <email@hidden>
  • Prev by Date: Re: [NSSound isPlaying] fails to indicate sound termination in Lion
  • Next by Date: Re: ARC Extending Lifetime of Objects
  • Previous by thread: Re: ARC Extending Lifetime of Objects
  • Next by thread: Re: Profound UITableView rendering-performance problem, but only at certain positions? mostly resolved
  • Index(es):
    • Date
    • Thread