On Jul 3, 2009, at 2:45 PM, Brian Slick wrote:
So now I either need to figure out how to make my scenarios all work
with a single identifier, or I may just go ahead with the code-only
cell I just built in response to the performance issue. If would be
nice if there was some kind of queueW
On Jul 3, 2009, at 4:39 PM, mmalc Crawford wrote:
On Jul 3, 2009, at 11:54 AM, Brian Slick wrote:
I did make a slight adjustment to the technique - most
significantly the omitting of the identifier in the XIB file,
This is actually a very significant factor.
If you haven't set an identifie
On Jul 3, 2009, at 11:54 AM, Brian Slick wrote:
So, if TaggedLocations was flying while mine was sucking, I'd
probably concede that what I was doing was wrong (and would probably
need more custom cells). But since neither one is performing very
well, and I can't find any significant diffe
Well, at first I really liked this technique, and it seems simple
enough. I restructured my program to use it, and in the simulator all
went well. Then I uploaded to the phone (1st-gen) and saw absolutely
horrid scrolling performance. I fired up the CA tool, and saw numbers
that were wel
On Jun 30, 2009, at 4:36 PM, Brian Slick wrote:
Does the first line mean that I cannot reuse the XIB-based cells in
different view controllers?
No. As long as the view controllers all provide the same API (the
actions and outlets) you use in the nib file, then the actual class
doesn't r
One more question about this approach...
On Jun 26, 2009, at 9:08 PM, mmalc Crawford wrote:
In the cell's nib file:
The class of the File's Owner should be your table view controller
class.
Set an identifier for the cell.
Connect the appropriate outlet from File's Owner to t
On Jun 26, 2009, at 7:20 PM, Brian Slick wrote:
Please pardon my noobness, but could you expand a little on how this
works? I'm assuming that the first line somehow assigns the <#cell
outlet property#>, since I don't see how else this could work, but I
sure don't see how that actually hap
On Jun 26, 2009, at 9:08 PM, mmalc Crawford wrote:
if (cell == nil) {
[[NSBundle mainBundle] loadNibNamed:@"<#Your nib file name#>"
owner:self options:nil];
cell = <#cell outlet property#>;
self.<#cell outlet property#> = nil;
On Jun 24, 2009, at 11:30 PM, Bryan Hansen wrote:
I'd like to add a custom button to my own custom tableview subclass
that will perform an action on the tableviewcontroller class. This
is pretty much identical to the way accessoryviews call a method on
the tableviewdelegate when it is tappe
On Jun 25, 2009, at 12:36 PM, Alexander Spohr wrote:
Am 25.06.2009 um 12:20 schrieb WT:
On Jun 25, 2009, at 11:46 AM, Alexander Spohr wrote:
Of course, you are right. I forgot that the OP wanted something
like an accessory which needs to be repetitive.
Even with a custom cell with no extr
Am 25.06.2009 um 12:20 schrieb WT:
On Jun 25, 2009, at 11:46 AM, Alexander Spohr wrote:
Of course, you are right. I forgot that the OP wanted something
like an accessory which needs to be repetitive.
Even with a custom cell with no extra controls, you'd need to return
a different cell ob
On Jun 25, 2009, at 11:46 AM, Alexander Spohr wrote:
Am 25.06.2009 um 10:54 schrieb WT:
On Jun 25, 2009, at 10:26 AM, Alexander Spohr wrote:
Why didn’t you put the cell into the controllers nib?
Make an outlet in your controller to reach the cell and just
return it when you need it?
Beca
Am 25.06.2009 um 10:54 schrieb WT:
On Jun 25, 2009, at 10:26 AM, Alexander Spohr wrote:
Why didn’t you put the cell into the controllers nib?
Make an outlet in your controller to reach the cell and just return
it when you need it?
Because -tableView:cellForRowAtIndexPath: needs to return
On Jun 25, 2009, at 10:26 AM, Alexander Spohr wrote:
Am 25.06.2009 um 10:16 schrieb WT:
I had exactly the same problem and here's how I solved it.
Why didn’t you put the cell into the controllers nib?
Make an outlet in your controller to reach the cell and just return
it when you need it?
Am 25.06.2009 um 10:16 schrieb WT:
I had exactly the same problem and here's how I solved it.
Why didn’t you put the cell into the controllers nib?
Make an outlet in your controller to reach the cell and just return it
when you need it?
The second nib seems to much work. And you get a spe
Hi Bryan,
I had exactly the same problem and here's how I solved it. I have a
custom table view cell in a separate nib file whose File Owner's class
is the table view controller class. I then have an IB action defined
in the table view controller class and I link the button in the cell
ni
Set your controller as the buttons taget:
– addTarget:action:forControlEvents:
UIControlEventTouchUpInside
atze
Am 25.06.2009 um 08:30 schrieb Bryan Hansen:
I'd like to add a custom button to my own custom tableview subclass
that will perform an action on the tableviewcontroller cla
17 matches
Mail list logo
