我试图实现滑动删除,并在ListView
使用SwipeToDismissUndoList延伸库罗马Nurik的SwipeToDismiss样品。
我的问题是在删除动画。 由于ListView
由支持CursorAdapter
,动画触发onDismiss
回调onAnimationEnd
但这意味着在动画运行和之前自行复位CursorAdapter
与删除更新。
这最终看起来像一个闪烁的地方,他们通过滑开删除笔记的用户,则该视图是回来的一瞬间,然后消失,因为CursorAdapter
回升中的数据变化。
这里是我的OnDismissCallback
:
private SwipeDismissList.OnDismissCallback dismissCallback =
new SwipeDismissList.OnDismissCallback() {
@Override
public SwipeDismissList.Undoable onDismiss(ListView listView, final int position) {
Cursor c = mAdapter.getCursor();
c.moveToPosition(position);
final int id = c.getInt(Query._ID);
final Item item = Item.findById(getActivity(), id);
if (Log.LOGV) Log.v("Deleting item: " + item);
final ContentResolver cr = getActivity().getContentResolver();
cr.delete(Items.buildItemUri(id), null, null);
mAdapter.notifyDataSetChanged();
return new SwipeDismissList.Undoable() {
public void undo() {
if (Log.LOGV) Log.v("Restoring Item: " + item);
ContentValues cv = new ContentValues();
cv.put(Items._ID, item.getId());
cv.put(Items.ITEM_CONTENT, item.getContent());
cr.insert(Items.CONTENT_URI, cv);
}
};
}
};
Answer 1:
我知道这个问题已经被标记为“回答”,但正如我在评论中指出,与使用MatrixCursor的问题是,它的效率太低。 复制除了要被删除的行的所有行意味着行删除运行在线性时间(在项目的数量线性在列表视图)。 对于大数据和较慢的手机,这可能是不可接受的。
另一种方法是实现自己的AbstractCursor忽略被删除的行。 这导致在一定的时间和可以忽略不计的性能损失绘制时假行删除运行。
实现示例:
public class CursorWithDelete extends AbstractCursor {
private Cursor cursor;
private int posToIgnore;
public CursorWithDelete(Cursor cursor, int posToRemove)
{
this.cursor = cursor;
this.posToIgnore = posToRemove;
}
@Override
public boolean onMove(int oldPosition, int newPosition)
{
if (newPosition < posToIgnore)
{
cursor.moveToPosition(newPosition);
}
else
{
cursor.moveToPosition(newPosition+1);
}
return true;
}
@Override
public int getCount()
{
return cursor.getCount() - 1;
}
@Override
public String[] getColumnNames()
{
return cursor.getColumnNames();
}
//etc.
//make sure to override all methods in AbstractCursor appropriately
按照所有的步骤,除了之前:
- 在SwipeDismissList.OnDismissCallback.onDismiss(),创建新CursorWithDelete。
- 交换了新的光标
Answer 2:
我觉得SwipeToDismissUndoList不利于基于游标的适配器。 由于适配器依靠来自内容提供商的变化( setNotificationUri()
或registerContentObserver()
...)来更新UI。 当数据是否可用你不知道。 这就是你面临的问题。
我觉得有点像一招。 您可以使用MatrixCursor
。
- 在
onLoadFinished(Loader, Cursor)
,你不断从内容提供商返回游标的引用。 您需要手动后关闭它。 - 在
SwipeDismissList.OnDismissCallback.onDismiss()
创建新MatrixCursor
,复制从当前光标的所有项目,除了要被删除的项目。 - 新创建的矩阵光标设在适配器
swapCursor()
未 changeCursor()
由于swapCursor()
不关闭旧光标。 你需要保持开放,使装载机工作正常。 - 现在的UI更新,您对呼叫
getContentResolver().delete()
和实际删除用户要删除的项目。 当内容提供商完成删除数据时,它会通知原光标重新加载数据。 确保关闭你换原来的光标。 例如:
private Cursor mOrgCursor; @Override public void onLoadFinished(Loader<Cursor> loader, Cursor data) { if (mOrgCursor != null) mOrgCursor.close(); mOrgCursor = data; mAdapter.changeCursor(mOrgCursor); } @Override public void onLoaderReset(Loader<Cursor> loader) { if (mOrgCursor != null) { mOrgCursor.close(); mOrgCursor = null; } mAdapter.changeCursor(null); }
- 不要担心矩阵光标,
changeCursor()
将其关闭。
Answer 3:
嘿,我有一个类似的问题,解决了这个样子,希望它可以帮助你:
我用什么切特·哈泽显示在此devbyte: http://www.youtube.com/watch?v=YCHNAi9kJI4
这是非常相似,罗马的代码,但在这里,他用的是ViewTreeObserver,等你以后从适配器删除的项目,但在此之前的列表将被重新绘制,你有时间的动画缩小差距,也不会闪烁。 另一个不同之处是,他在适配器设置监听到每个视图(项目)名单,而不是ListView控件本身。
所以,我的代码示例:
这是ListActivity的onCreate,在这里我通过监听到适配器没有什么特别的:
ListAdapterTouchListener listAdapterTouchListener = new ListAdapterTouchListener(getListView());
listAdapter = new ListAdapter(this,null,false,listAdapterTouchListener);
这里是ListAdapter的一部分(这是我自己的适配器扩展CursorAdapter的),我通过监听的构造函数,
private View.OnTouchListener onTouchListener;
public ListAdapter(Context context, Cursor c, boolean autoRequery,View.OnTouchListener listener) {
super(context, c, autoRequery);
onTouchListener = listener;
}
然后在NewView的方法我将其设置为视图:
@Override
public View newView(final Context context, Cursor cursor, ViewGroup parent) {
View view = layoutInflater.inflate(R.layout.list_item,parent,false);
// here should be some viewholder magic to make it faster
view.setOnTouchListener(onTouchListener);
return view;
}
监听器大多一样在视频中显示的代码,我不使用backgroundcontainer不过这只是我的选择。 所以animateRemoval有什么有趣的部分,那就是:
private void animateRemoval(View viewToRemove){
for(int i=0;i<listView.getChildCount();i++){
View child = listView.getChildAt(i);
if(child!=viewToRemove){
// since I don't have stableIds I use the _id from the sqlite database
// I'm adding the id to the viewholder in the bindView method in the ListAdapter
ListAdapter.ViewHolder viewHolder = (ListAdapter.ViewHolder)child.getTag();
long itemId = viewHolder.id;
itemIdTopMap.put(itemId, child.getTop());
}
}
// I'm using content provider with LoaderManager in the activity because it's more efficient, I get the id from the viewholder
ListAdapter.ViewHolder viewHolder = (ListAdapter.ViewHolder)viewToRemove.getTag();
long removeId = viewHolder.id;
//here you remove the item
listView.getContext().getContentResolver().delete(Uri.withAppendedPath(MyContentProvider.CONTENT_ID_URI_BASE,Long.toString(removeId)),null,null);
// after the removal get a ViewTreeObserver, so you can set a PredrawListener
// the rest of the code is pretty much the same as in the sample shown in the video
final ViewTreeObserver observer = listView.getViewTreeObserver();
observer.addOnPreDrawListener(new ViewTreeObserver.OnPreDrawListener() {
@Override
public boolean onPreDraw() {
observer.removeOnPreDrawListener(this);
boolean firstAnimation = true;
for(int i=0;i<listView.getChildCount();i++){
final View child = listView.getChildAt(i);
ListAdapter.ViewHolder viewHolder = (ListAdapter.ViewHolder)child.getTag();
long itemId = viewHolder.id;
Integer startTop = itemIdTopMap.get(itemId);
int top = child.getTop();
if(startTop!=null){
if (startTop!=top) {
int delta=startTop-top;
child.setTranslationY(delta);
child.animate().setDuration(MOVE_DURATION).translationY(0);
if(firstAnimation){
child.animate().setListener(new Animator.AnimatorListener() {
@Override
public void onAnimationStart(Animator animation) {
}
@Override
public void onAnimationEnd(Animator animation) {
swiping=false;
listView.setEnabled(true);
}
@Override
public void onAnimationCancel(Animator animation) {
}
@Override
public void onAnimationRepeat(Animator animation) {
}
});
firstAnimation=false;
}
}
}else{
int childHeight = child.getHeight()+listView.getDividerHeight();
startTop = top+(i>0?childHeight:-childHeight);
int delta = startTop-top;
child.setTranslationY(delta);
child.animate().setDuration(MOVE_DURATION).translationY(0);
if(firstAnimation){
child.animate().setListener(new Animator.AnimatorListener() {
@Override
public void onAnimationStart(Animator animation) {
}
@Override
public void onAnimationEnd(Animator animation) {
swiping=false;
listView.setEnabled(true);
}
@Override
public void onAnimationCancel(Animator animation) {
}
@Override
public void onAnimationRepeat(Animator animation) {
}
});
firstAnimation=false;
}
}
}
itemIdTopMap.clear();
return true;
}
});
}
希望这可以帮助你,它的工作很好,我! 你真的应该看devbyte,这对我帮助很大!
Answer 4:
在此张贴回答的时刻,我已经试过从这个线索的所有上市的做法。 CursorWrapper是从性能上来说最有效的,但不幸的是没有安全,因为不能保证驳回项目的那个位置是稳定的(如果数据可以从另一来源由后台同步改变,例如)。 Alternatevely,你可以试试我的简单实现基地光标适配器:
/*
* Copyright (C) 2014. Victor Kosenko (http://qip-blog.eu.org)
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
// your package here
import android.content.Context;
import android.database.Cursor;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.CursorAdapter;
import com.google.api.client.util.Sets;
import java.util.Set;
/**
* This is basic implementation of swipable cursor adapter that allows to skip displaying dismissed
* items by replacing them with empty view. This adapter overrides default implementation of
* {@link #getView(int, android.view.View, android.view.ViewGroup)}, so if you have custom
* implementation of this method you should review it according to logic of this adapter.
*
* @author Victor Kosenko
*/
public abstract class BaseSwipableCursorAdapter extends CursorAdapter {
protected static final int VIEW_ITEM_NORMAL = 0;
protected static final int VIEW_ITEM_EMPTY = 1;
protected Set<Long> pendingDismissItems;
protected View emptyView;
protected LayoutInflater inflater;
/**
* If {@code true} all pending items will be removed on cursor swap
*/
protected boolean flushPendingItemsOnSwap = true;
/**
* @see android.widget.CursorAdapter#CursorAdapter(android.content.Context, android.database.Cursor, boolean)
*/
public BaseSwipableCursorAdapter(Context context, Cursor c, boolean autoRequery) {
super(context, c, autoRequery);
init(context);
}
/**
* @see android.widget.CursorAdapter#CursorAdapter(android.content.Context, android.database.Cursor, int)
*/
protected BaseSwipableCursorAdapter(Context context, Cursor c, int flags) {
super(context, c, flags);
init(context);
}
/**
* Constructor with {@code null} cursor and enabled autoRequery
*
* @param context The context
*/
protected BaseSwipableCursorAdapter(Context context) {
super(context, null, true);
init(context);
}
/**
* @param context The context
* @param flushPendingItemsOnSwap If {@code true} all pending items will be removed on cursor swap
* @see #BaseSwipableCursorAdapter(android.content.Context)
*/
protected BaseSwipableCursorAdapter(Context context, boolean flushPendingItemsOnSwap) {
super(context, null, true);
init(context);
this.flushPendingItemsOnSwap = flushPendingItemsOnSwap;
}
protected void init(Context context) {
inflater = LayoutInflater.from(context);
pendingDismissItems = Sets.newHashSet();
emptyView = new View(context);
}
@Override
public View getView(int position, View convertView, ViewGroup parent) {
if (!getCursor().moveToPosition(position)) {
throw new IllegalStateException("couldn't move cursor to position " + position);
}
if (isPendingDismiss(position)) {
return emptyView;
} else {
return super.getView(position, convertView, parent);
}
}
@Override
public int getViewTypeCount() {
return 2;
}
@Override
public int getItemViewType(int position) {
return pendingDismissItems.contains(getItemId(position)) ? VIEW_ITEM_EMPTY : VIEW_ITEM_NORMAL;
}
/**
* Add item to pending dismiss. This item will be ignored in
* {@link #getView(int, android.view.View, android.view.ViewGroup)} when displaying list of items
*
* @param id Id of item that needs to be added to pending for dismiss
* @return {@code true} if this item already in collection if pending items, {@code false} otherwise
*/
public boolean putPendingDismiss(Long id) {
return pendingDismissItems.add(id);
}
/**
* Confirm that specified item is no longer present in underlying cursor. This method should be
* called after the fact of removing this item from result set of underlying cursor.
* If you're using flushPendingItemsOnSwap flag there is no need to call this method.
*
* @param id Id of item
* @return {@code true} if this item successfully removed from pending to dismiss, {@code false}
* if it's not present in pending items collection
*/
public boolean commitDismiss(Long id) {
return pendingDismissItems.remove(id);
}
/**
* Check if this item should be ignored
*
* @param position Cursor position
* @return {@code true} if this item should be ignored, {@code false} otherwise
*/
public boolean isPendingDismiss(int position) {
return getItemViewType(position) == VIEW_ITEM_EMPTY;
}
public boolean isFlushPendingItemsOnSwap() {
return flushPendingItemsOnSwap;
}
/**
* Automatically flush pending items when calling {@link #swapCursor(android.database.Cursor)}
*
* @param flushPendingItemsOnSwap If {@code true} all pending items will be removed on cursor swap
*/
public void setFlushPendingItemsOnSwap(boolean flushPendingItemsOnSwap) {
this.flushPendingItemsOnSwap = flushPendingItemsOnSwap;
}
@Override
public Cursor swapCursor(Cursor newCursor) {
if (flushPendingItemsOnSwap) {
pendingDismissItems.clear();
}
return super.swapCursor(newCursor);
}
}
它基于的HashSet和默认项ID(getItemId()),所以性能不应该是一个问题,因为含有()方法有O(1)的时间复杂度和实际设置将包含零个或一个项目的大部分时间。 此外它取决于番石榴。 如果您使用的不是番石榴,只需更换上线91集建筑。
要使用它,在你的项目,你可以只是继承这个类来代替的CursorAdapter并添加几行代码在onDismiss()(如果你使用EnhancedListView或类似的库):
@Override
public EnhancedListView.Undoable onDismiss(EnhancedListView enhancedListView, int i) {
adapter.putPendingDismiss(id);
adapter.notifyDataSetChanged();
...
}
如果你使用的列表分隔(因为该适配器显示空视图,而不是驳回项目)这种解决方案将无法工作。 你应该在你的项目布局增加利润,使项目之间的间距,并包括在项目布局分隔。
此代码可以在未来的更新,所以我已经张贴在github上要点: https://gist.github.com/q1p/0b95633ab9367fb86785
另外,我想推荐你不要在你的例子:)使用I /在主线程O操作一样
Answer 5:
刚来到这里同样的问题,并与伊曼纽尔Moecklin提供的代码完美,轻松解决了。
这真的很简单:里面的onDismiss方法,这样做:
//Save cursor for later
Cursor cursor = mAdapter.getCursor();
SwipeToDeleteCursorWrapper cursorWrapper = new SwipeToDeleteCursorWrapper(mAdapter.getCursor(), reverseSortedPositions[0]);
mAdapter.swapCursor(cursorWrapper);
//Remove the data from the database using the cursor
然后创建SwipteToDeleteCursorWrapper由伊曼纽尔写道:
public class SwipeToDeleteCursorWrapper extends CursorWrapper
{
private int mVirtualPosition;
private int mHiddenPosition;
public SwipeToDeleteCursorWrapper(Cursor cursor, int hiddenPosition)
{
super(cursor);
mVirtualPosition = -1;
mHiddenPosition = hiddenPosition;
}
@Override
public int getCount()
{
return super.getCount() - 1;
}
@Override
public int getPosition()
{
return mVirtualPosition;
}
@Override
public boolean move(int offset)
{
return moveToPosition(getPosition() + offset);
}
@Override
public boolean moveToFirst()
{
return moveToPosition(0);
}
@Override
public boolean moveToLast()
{
return moveToPosition(getCount() - 1);
}
@Override
public boolean moveToNext()
{
return moveToPosition(getPosition() + 1);
}
@Override
public boolean moveToPosition(int position)
{
mVirtualPosition = position;
int cursorPosition = position;
if (cursorPosition >= mHiddenPosition)
{
cursorPosition++;
}
return super.moveToPosition(cursorPosition);
}
@Override
public boolean moveToPrevious()
{
return moveToPosition(getPosition() - 1);
}
@Override
public boolean isBeforeFirst()
{
return getPosition() == -1 || getCount() == 0;
}
@Override
public boolean isFirst()
{
return getPosition() == 0 && getCount() != 0;
}
@Override
public boolean isLast()
{
int count = getCount();
return getPosition() == (count - 1) && count != 0;
}
@Override
public boolean isAfterLast()
{
int count = getCount();
return getPosition() == count || count == 0;
}
}
就这样!
Answer 6:
(这个答案是关于罗马Nuriks库 ,因此,从支库,它应该是相似的)。
这个问题是因为这些库要回收已删除的意见。 行项目动画消失后基本上,库重置为原来的位置,并期待,这样的ListView可以重复使用它。 有两种解决方法。
解决方法1
在performDismiss(...)
库的方法,发现,重置驳回视图中的代码部分。 这是部分:
ViewGroup.LayoutParams lp;
for (PendingDismissData pendingDismiss : mPendingDismisses) {
// Reset view presentation
pendingDismiss.view.setAlpha(1f);
pendingDismiss.view.setTranslationX(0);
lp = pendingDismiss.view.getLayoutParams();
lp.height = originalHeight;
pendingDismiss.view.setLayoutParams(lp);
}
mPendingDismisses.clear();
删除此部分,并把它放在一个单独的public
方法:
/**
* Resets the deleted view objects to their
* original form, so that they can be reused by the
* listview. This should be called after listview has
* the refreshed data available, e.g., in the onLoadFinished
* method of LoaderManager.LoaderCallbacks interface.
*/
public void resetDeletedViews() {
ViewGroup.LayoutParams lp;
for (PendingDismissData pendingDismiss : mPendingDismisses) {
// Reset view presentation
pendingDismiss.view.setAlpha(1f);
pendingDismiss.view.setTranslationX(0);
lp = pendingDismiss.view.getLayoutParams();
lp.height = originalHeight;
pendingDismiss.view.setLayoutParams(lp);
}
mPendingDismisses.clear();
}
最后,在您的主要活动,调用此方法时,新的光标已准备就绪。
解决方案2
忘掉回收行项目(这只是一个行,毕竟)。 而不是重置视图和制备它用于再循环,以某种方式将其标记为在染色performDismiss(...)
的文库的方法。
然后填写你的ListView(通过覆盖适配器的时候getView(View convertView, ...)
方法),请检查上标记convertView
对象。 如果有,请不要使用convertView
。 例如,你可以做(下面这段是伪代码)
if (convertView is marked as stained) {
convertView = null;
}
return super.getView(convertView, ...);
Answer 7:
基于ü阿瓦洛斯答案我实现光标包装物处理多个删除位置。 但是解决方案还没有完全测试,可能包含错误。 使用这样的,当你设置一个游标
mAdapter.changeCursor(new CursorWithDelete(returnCursor));
如果你想从列表中隐藏的一些项目
CursorWithDelete cursor = (CursorWithDelete) mAdapter.getCursor();
cursor.deleteItem(position);
mAdapter.notifyDataSetChanged();
CusrsorWithDelete.java
import java.util.ArrayList;
import java.util.Collections;
import java.util.List;
import android.database.AbstractCursor;
import android.database.Cursor;
public class CursorWithDelete extends AbstractCursor {
private List<Integer> positionsToIgnore = new ArrayList<Integer>();
private Cursor cursor;
public CursorWithDelete(Cursor cursor) {
this.cursor = cursor;
}
@Override
public boolean onMove(int oldPosition, int newPosition) {
cursor.moveToPosition(adjustPosition(newPosition));
return true;
}
public int adjustPosition(int newPosition) {
int ix = Collections.binarySearch(positionsToIgnore, newPosition);
if (ix < 0) {
ix = -ix - 1;
} else {
ix++;
}
int newPos;
int lastRemovedPosition;
do {
newPos = newPosition + ix;
lastRemovedPosition = positionsToIgnore.size() == ix ? -1 : positionsToIgnore.get(ix);
ix++;
} while (lastRemovedPosition >= 0 && newPos >= lastRemovedPosition);
return newPos;
}
@Override
public int getCount() {
return cursor.getCount() - positionsToIgnore.size();
}
@Override
public String[] getColumnNames() {
return cursor.getColumnNames();
}
@Override
public String getString(int column) {
return cursor.getString(column);
}
@Override
public short getShort(int column) {
return cursor.getShort(column);
}
@Override
public int getInt(int column) {
return cursor.getInt(column);
}
@Override
public long getLong(int column) {
return cursor.getLong(column);
}
@Override
public float getFloat(int column) {
return cursor.getFloat(column);
}
@Override
public double getDouble(int column) {
return cursor.getDouble(column);
}
@Override
public boolean isNull(int column) {
return cursor.isNull(column);
}
/**
* Call if you want to hide some position from the result
*
* @param position in the AdapterView, not the cursor position
*/
public void deleteItem(int position) {
position = adjustPosition(position);
int ix = Collections.binarySearch(positionsToIgnore, position);
positionsToIgnore.add(-ix - 1, position);
}
}
文章来源: CursorAdapter backed ListView delete animation “flickers” on delete