Luke Scott
Luke Scott
There are already some animation issues that I haven't been able to fix. The reason, I suspect, is that delete and insert is just a shorter animation. With a batch,...
That's a new issue. With the insert/delete or move, the issue is still the same. On my fork I have an experimental patch that either forces a layout change, or...
@ToddManUtah Try [this fork](https://github.com/lukescott/LXReorderableCollectionViewFlowLayout), and if you still have the same problem, open an issue (and link to this one) and I'll take a look at it when I get...
@ALulzyApprentice When I have a chance I'll look into this and see what I can come up with. If you could try [this fork](https://github.com/lukescott/LXReorderableCollectionViewFlowLayout) and verify it's still an issue,...
Are you using a NSMutableArray as your data source, and then mutating it on each data source delegate call? I'm unclear as to why you need to compare anything. Should...
Ok, I'm still not sure what you mean. The sample project included should work correctly. There should be no need to do any comparisons - If a single item moves...
This issue has been fixed in https://github.com/lukescott/LXReorderableCollectionViewFlowLayout/issues/3. Just waiting on confirmation, then I'll push it to my master branch and make it part of pull request https://github.com/lxcid/LXReorderableCollectionViewFlowLayout/pull/14.
It turns out this was more difficult to fix. The insert/delete (or move) commands cause animations themselves. The fix, doing a blank performBatchUpdates, simply stopped all the animations, which caused...
@lxcid, I'm not sure if that's possible without completely changing your delegate/dataSource calls. LXReorderableCollectionViewFlowLayout assumes that the data source changes for every movement, and DraggableCollectionView assumes that it doesn't. The...
@lxcid That sounds good. Although it might be best for you to update the README. I've already changed it on my fork, and I think you probably want to present...