Databases
StackOverflow2013
Postsdbo
POHow to avoid swipe to delete calling setEditing at the UITableViewCell
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
    primarykey
    data
    text
    <p>I know, that when I implement <code>tableView:willBeginEditingRowAtIndexPath:</code>and <code>tableView:didEndEditingRowAtIndexPath:</code>, a swipe-to-delete does not call <code>setEditing:animated:</code> at my <code>UITableViewController</code> (being the delegate of the <code>UITableView</code>).</p> <p>I have a custom <code>UITableViewCell</code> implementation that does a little UI rearrangements when going to edit mode. I wanted to be smart and implemented these changes in <code>setEditing:animated:</code> at the table view cell implementation itself (which obviously makes sense).</p> <p>However, when swiping to delete, I still get a call to <code>setEditing:animated:</code> at my table view cell implementation. And I have no parameter that tells me that I am swiping. The call stack also shows none of my own methods that would give me a chance to do something. It shows that <code>setEditing:animated</code> is called at the <code>UITableView</code>. The only thing obviously is, that it is not called at the delegate (my controller in this case).</p> <p>Of course, I could set a flag at the cell in <code>tableView:willBeginEditingRowAtIndexPath:</code> that tells it that the next <code>setEditing</code> call will be for a swipe, but that does not sound like good style.</p> <p><strong>Edit</strong>: it doesn't even work, because it is not guaranteed that <code>tableView:didEndEditingRowAtIndexPath:</code> is called, so I cannot set the flag back.</p> <p>Any ideas how to solve this issue elegantly?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBjörn Landmesser
    1. USBjörn Landmesser
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
      1. USBjörn Landmesser
      1. VTBountyStart
    1. COI'm not sure if I understand correctly. So you still want to do something in your UITableViewCell's setEditing:animated:, right? If not, does this link help? http://stackoverflow.com/questions/969313/uitableview-disable-swipe-to-delete-but-still-have-delete-in-edit-mode
      singulars
      1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
      1. USphi
    2. COI want to have swipe-to-delete enabled. But I want to be able to distinguish between "real" edit mode and the "pseudo" edit mode that is set for swipe-to-delete. In the `UITableViewDelegate` I can distinguish both, because `setEditing:animated:` is not called when swiping to delete. However I am not able to make a difference in the `UITableViewCell` implementation. Or am I somehow?
      singulars
      1. POHow to avoid swipe to delete calling setEditing at the UITableViewCell
      1. USBjörn Landmesser
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload