1

I've a simple question but I cannot find a clear answer around the web.

Suppose I have a custom 

UITableViewCell

With the default disclosure detail button that take to a detail view controller.

Is it good to have secondary, custom button that, when tapped, fires another action rather than presenting the detail view controller?

Or it could be an HIG violation?

any suggestion very appreciated.

Simone
  • 233
  • 1
  • 8

2 Answers2

0

Where would you like to put another button? Maybe the simplest thing to do is put the other action in 

-(void) tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
Dunja Lalic
  • 752
  • 13
  • 26
0

I probably mis-explained.

Here is a raw image. It may help claryfing the question: enter image description here

Simone
  • 233
  • 1
  • 8
  • 1
    After googling and watching hundreds of iOS common patterns, I come to a conclusion: having an UIButton on a selectable UITableViewCell may not violate any Apple HIG, but it's a very very bad experience for the user. – Simone Mar 10 '11 at 16:47