Closed andrei4002 closed 11 years ago
Do you update your data model after releasing the cell to it's new position?
Well, I can replicate the bug in your demo project (I can make a video tomorrow if you'd like)
Try grabbing a cell and throw it somehow at the bottom, like you mean to put it somewhere below the current visible screen (you might not replicate it the first time but if you try a few times you'll probably get it)
Would be great if you can send me a small video. Was not able to reproduce.
sure, here's a link
I took the source of this project and stripped it down. I still don’t know what’s the cause of that bug but it seems it doesn’t appear in my version any more. Give me some more days and I might find it.
But I found another bug that may relate to this one because it also causes duplicates:
When you grab a cell and autoscroll down a bit then scroll up again where your dragged cell once sat, it reappears in the table as if nothing had happened.
[ one ] --- <-
[ two ] | |
[ three ] | |
[ ... ] | |
[ ... ] |_____|
scroll down until [ one ] gets off the visible area
then scroll up again
you would expect that [ one ] is not there anymore (because you are currently still dragging it around)
but instead everything appears as if nothing had happened
what you would expect:
[ two ]
[ blank ]
[ three ]
[ ... ]
[ ... ]
instead it’s like this:
[ one ]
[ blank ]
[ three ]
[ ... ]
[ ... ]
So when you release the dragged cell you have two of them. Refresh the table view (or: scroll down and up again) and everything is as it should be.
This issue is fixed within the latest commit v1.1.2
I tried v1.1 and the fixes from OpenFibers and I can still see duplicates
for v1.1 you just need to drag a cell and throw it just at the bottom side of the table
for OpenFibers' fix i seem to get duplicates when i drag a cell from bottom to top, while scrolling fast (the first cells don't update, the datasource is updated correctly). this doesn't seem to happen when I drag from top to bottom
can't figure out why this is happening though