iOS Disclosure Indicator and Detail Buttons on same table

[StevenHu]

I have a table in which one cell goes to another table, and thus uses a disclosure indicator icon. All the rest of the cells use the detail disclosure button.

How do I specify the one disclosure indicator for the one cell when the method uses *indexpath for all the cells? Am I supposed to use a switch for this situation?

Thanks,
Steve

 

[KoolStar]

You could just use an if statement. If that cells text matches what your looking for then set the cell indicator. If not set it to the other indicator.

 

[dejo]

How do I specify the one disclosure indicator for the one cell when the method uses *indexpath for all the cells? Am I supposed to use a switch for this situation?

You could. A simple if might even suffice. And don't forget that the indexPath contains both unique section and row for each cell.

 

[StevenHu]

You could just use an if statement. If that cells text matches what your looking for then set the cell indicator. If not set it to the other indicator.

OK, so I'll do an if/else after the "if (cell == nil)" line.
Hmmm... wrong syntax when attempted. I'll keep trying.

Thanks!

 

[dejo]

OK, so I'll do an if/else after the "if (cell == nil)" line.

Just to be clear, you'll probably want to be doing the logic outside of that if statement, since it only executes when a cell is not being reused (i.e. needs to be instantiated). You're gonna want to make sure you are setting the right indicator for reused cells as well. Otherwise, you may find cells with the wrong indicator appearing.

 

[KoolStar]

If I were you I would set it right before i set the text in the cell.

 

[StevenHu]

I can't seem to get the if() part right. if(indexPath == 1) generates a warning and doesn't make a difference with the icons. Don't know what syntax to use to check for the view controller name.

Thanks,
Steve

 

[KoolStar]

You have to get the row out of the indexpath first.

 

[dejo]

if(indexPath == 1) generates a warning...

Correct. That's because indexPath is not an integer, it's an NSIndexPath.

 

[StevenHu]

You have to get the row out of the indexpath first.

This helped. I used

NSUInteger row = [indexPath row]; 
if (row ==1)

The icon changed on the side as I wanted, but the above generated two warnings. The first line was "initialization makes pointer from integer without a cast," and the second line was a "comparison between pointer and integer."

I'm going too fast! Got to slow down and think it through!

 

[dejo]

I'm going too fast! Got to slow down and think it through!

Please do!

 

[StevenHu]

OK, all I needed was

if (indexPath.row ==1)

No warnings or errors and the icons appear correctly!

Thanks!
STeve

 

[dejo]

P.S.

NSUInteger row = [indexPath row]; 
if (row ==1)

...but the above generated two warnings.

The above code won't generate any warnings. But it will generate those if it's:

NSUInteger *row = [indexPath row]; 
if (row ==1)

Make sure the code snippets you are including in your posts are the same as in your code. Otherwise, you are just going to confuse those trying to help you.

P.P.S. Please use

 tags.

 

[StevenHu]

Sorry about that, Dejo! My Mac Mini is not connected to the Internet here, so I scoot to the PC and post from there.

Thanks,
Steve

 

[North Bronson]

Just to be clear, you'll probably want to be doing the logic outside of that if statement, since it only executes when a cell is not being reused (i.e. needs to be instantiated). You're gonna want to make sure you are setting the right indicator for reused cells as well. Otherwise, you may find cells with the wrong indicator appearing.

An alternative might be to put all that logic in the "(if cell == nil)" statement, but then use different reuse identifiers for each different case.

 

[dejo]

An alternative might be to put all that logic in the "(if cell == nil)" statement, but then use different reuse identifiers for each different case.

Agreed. That's a suitable alternative.

 

[StevenHu]

An alternative might be to put all that logic in the "(if cell == nil)" statement, but then use different reuse identifiers for each different case.

That's out of my knowledge zone, unfortunately. I'm still learning as I go!

Thanks,
Steve

 

[North Bronson]

A handy alternative to hard-coding these numbers is to add a Boolean to your table data. If you are using an array of dictionaries to populate your table, you can add a Boolean to certain "rows". Then, instead of checking to see if the current row corresponds to "1", you can check the appropriate Boolean.

This will just make it easier if you ever have to rearrange your table data. Using a PLIST is just a matter of dragging things around without having to go back to this line and change the index of the special cell.