Paul Burke
Paul Burke
You can observe this in the sample app: 
@hzsweers This library uses the old drag and drop methods (View.OnDragListener). It was one of the motivators for me to write that article.
I had this issue until I published the Sheet. You must make it public using the "Share" button, but also from the File menu: "Publish to the web..."
Thanks! I'm going to try and set time aside to set this up this weekend.
Hey, this is a bit out of scope, but something I have considered. I am, mostly, trying to follow the Android APIs and docs, using `ACTION_GET_CONTENT` with `CATEGORY_OPENABLE` to return...
As mentioned in the article, `onItemMove` is called **every time** an item index changes. This means that for your example, it will call `onItemMove(A, B)` then `onItemMove(B, C)` This is...
`onItemMove` would never be called from with 0 as `fromPosition` and 2 as `toPosition`. As I explained above, an actual drag from 0 to 2 would call ``` onItemMove(0,1) onItemMove(1,2)...
Ah! You're saying that the items show properly, but the underlying data is not properly reflecting the change. Sorry, I had misread your issue. Re-opening.
I will be updating the code and article to make this correction. Thanks! Note, you can simplify to this: ``` @Override public boolean onItemMove(int fromPosition, int toPosition) { if (fromPosition...
Yeah, right now it is just defaulting to `Environment.getExternalStorageDirectory()`. This could be configurable though, so I will expose the base directory as an option in the next release. Feel free...