It sounds like you have a design problem if you want potentially large
numbers of sections but it isn't easy to calculate the size of said
sections. What are you really trying to do?
Luke
Sent from my iPhone.
On Dec 17, 2009, at 8:01 PM, Karolis Ramanauskas <[email protected]>
wrote:
Luke helped me with this a little bit, but, after experimenting, it
seams
there is more to it.
I guess there is still something I do not understand about this.
Yes, I can
set a huge number of rows. But I want them to be grouped into
sections.
However, UITableView wants to know exactly how many rows are in each
section
on load time, even for invisible sections. So, if I have a rule that
describes recurring events in my model, that means I would have to
expand
these and calculate, number of rows per section on load. If I have,
let's
say, 10,000 sections (to imitate the never-ending list) this may be
a costly
calculation. I assume there is no way around this, but limiting the
number
of sections to a lot lower numbers...
Peace.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
This email sent to [email protected]
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
