HPReorderTableView subclass shows a copy of the cell behind when the table view is its own data source

[dozel]

Hey, firstly, thank you so much for this project, great time saver.

I subclassed the tableview so that I could reuse it later. Unfortunately this caused a funny side effect: when I am in reordering mode, the reordered cell leaves behind a copy of itself. So instead of the white empty cell, you actually see a copy of the cell. Do you know why this might happen?

I was able to get rid of this effect by not subclassing the tableview, but that way did not allow me to override functions like canMoveRowAtIndexPath or canEditRowAtIndexPath. Any help would be greatly appreciated. Thanks!

[hpique]

Thanks @dozel. Can you provide a sample project with the error?

[dozel]

Hey @hpique , I've created a sample project you can download here:
https://dl.dropboxusercontent.com/u/16411938/ReorderTest.zip

[hpique]

Thanks @dozel. The problem is not the subclass, but making the table view its own data source. Essentially, the tableView:cellForRowAtIndexPath: swizzle in HPReorderTableView (which is responsible for setting the empty cell) is not being called.

This looks like a bug. I'll look into it as soon as I return from vacation. In the meantime, you can simply let your view controller be the data source.

[dozel]

When I do that, I cannot use certain methods like canMoveRowAtIndexPath. Do you know why that would happen?