I remember watching an Apple iOS video on performance for almost exactly the
same thing IIRC.
It's this video: Maximizing Your Application's Performance on iPhone
From: iPhone Development Essential Videos
You can get it in iTunes.
It's from the Developer on iTunes section.
+1, I was
On Fri, 18 Nov 2011 19:08:44 -0800, Laurent Daudelin laur...@nemesys-soft.com
said:
On Nov 18, 2011, at 18:48, Roland King wrote:
On Nov 19, 2011, at 10:38 AM, Conrad Shultz wrote:
On 11/18/11 3:29 PM, Laurent Daudelin wrote:
There isn't much special code in that UITableView subclass and
Hello.
I'm facing the task of fixing a problem occurring in one of the UITableView of
our app. The view displays cells of various height. Everything works fine,
except that we have a mechanism that when we reach the last cell at the bottom,
that cell will trigger loading more data and adding
I forgot to add to my previous message that the scrollview will resume its
dragging momentum if I touch and drag any other view.
Does that give a clue to anyone?
Thanks!
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
http://www.nemesys-soft.com/
On 11/18/11 3:29 PM, Laurent Daudelin wrote:
There isn't much special code in that UITableView subclass and not
much either in the UITableViewController so I'm a little bit at a
lost as to what could cause this. There is nothing fancy here, no
custom handling of touches and things like that,
On Nov 19, 2011, at 10:38 AM, Conrad Shultz wrote:
On 11/18/11 3:29 PM, Laurent Daudelin wrote:
There isn't much special code in that UITableView subclass and not
much either in the UITableViewController so I'm a little bit at a
lost as to what could cause this. There is nothing fancy here,
On Nov 18, 2011, at 18:48, Roland King wrote:
On Nov 19, 2011, at 10:38 AM, Conrad Shultz wrote:
On 11/18/11 3:29 PM, Laurent Daudelin wrote:
There isn't much special code in that UITableView subclass and not
much either in the UITableViewController so I'm a little bit at a
lost as to
Roland, Luke and David,
I think you're right and I misunderstood the dequeue…
I looked at the AdvancedTableViewCells sample. Each time the dequeue… doesn't
return a cell, it loads a new cell from a xib file, so, I guess, in effect
creating a new cell.
I'll have to bundle my cell that is
The typical idiom is to try to dequeue a reusable cell. If that returns nil,
create a new cell. No matter whether it was dequeued or created, configure the
cell (i.e., assign values to labels, configure decorations, etc.). Dequeuing
saves you the overhead of creating new views but you still
I've been banging my head on this for over a day now and I just can't find
what's wrong with my tableview and the tableview cells.
Basically, as you can see here:
http://nemesys.dyndns.biz/Images/iPhoneScreenshot.png
I have a table view made of 2 sections. Section 1 has only one tableview cell
Are you returning the same cell 4 times? That's not right. You're going to need
4 separate cell instances even if they are of the same class and layout. It
sounds like you might be taking 1 cell instance out of a nib and returning that
each time.
Luke
Sent from my iPhone.
On Jul 31, 2010,
Isn't the purpose of dequeueReusableCellWithIdentifier: of reusing tableview's
objects? I've used this in the past and it never failed me. The documentation
says For performance reasons, a table view's data source should generally
reuse UITableViewCell objects when it assigns cells to rows in
On Jul 31, 2010, at 10:25 PM, Laurent Daudelin wrote:
Isn't the purpose of dequeueReusableCellWithIdentifier: of reusing
tableview's objects? I've used this in the past and it never failed me. The
documentation says For performance reasons, a table view'€™s data source
should generally
I think you've missed the point of what Luke's saying. If
dequeueReusableCellWithIdentifier: returns nil then you create a cell with that
identifer, correct, and that cell can be recycled later by the tableview.
That's what the [ [ [ UITableViewCell ] alloc ] initWith... ] autorelease ]
does,
14 matches
Mail list logo
