IPhone UISwitch not appearing correctly in table cells

Question

I have a table cell with a UISwitch attached to it.
When you click the switch it works (but not without a bit of code to make it switch when the word 'on' and 'off' are actually clicked) but when the table cell itself is clicked the switch distorts like shown here:
http://img35.imageshack.us/img35/6510/picture1df.png
what is the correct way to make a table cell with a UISwitch?

Answer 1

The code you posted looks like it should work on 3.0 just fine.
I've tried a custom table cell and it did the same thing
Assuming your custom subclass was built and used correctly, the above tells me something is definitely wrong in the cell's environment.
Perhaps it's something to do with the selecting of the row method?
Well that's certainly the first place to look. The delegate method you posted looks kinky. I would comment out that method, then go back to the solutions that didn't work in the past and see if your tableView:didSelectRowAtIndexPath: hasn't been the problem all along.
In any case I would get rid of the deselect message in tableView:didSelectRowAtIndexPath:. What are you trying to accomplish there? If you simply want to disable all selections, you can just code tableView.allowsSelection=NO during setup. If you want to know the user's selection but don't want the cell to actually become selected, try something like this in the delegate:
- (NSIndexPath *)tableView:(UITableView *)tableView willSelectRowAtIndexPath:(NSIndexPath *)indexPath {
return nil;
If you want the cell to actually become selected, but don't want its appearance to change, try cell.selectionStyle=UITableViewCellSelectionStyleNone in tableView:cellForRowAtIndexPath:.
If tableView:didSelectRowAtIndexPath: turns out not to have been the problem, we'll need to look at the rest of your table view code. I've found the kind of problem you described is easily isolated once you have faith in some assumptions. In this case you just need to believe that both the subclass solution and the code in UICatalog will allow a UISwitch to display and operate perfectly. Once you believe that, you'll pay more attention to the rest of you code.
One excellent way to gain faith in the basic structure is to start a fresh testbed and, for example, use code similar to UICatalog to bring up a table view with a UISwitch in one or more cells. Once you see how easy it is to make that work, you can start backing in some of your more creative init, delegate and/or data source methods until you break the testbed.
- Ray