Listview上下滚动崩溃

利用CursorAdapter在ListView中显示Cursor中不同同类型的item,加载均正常,滚动时报如下错误:

11-28 15:18:16.703: E/InputEventReceiver(3155): Exception dispatching input event.
11-28 15:18:16.703: E/MessageQueue-JNI(3155): Exception in MessageQueue callback: handleReceiveCallback
11-28 15:18:16.707: E/MessageQueue-JNI(3155): java.lang.ArrayIndexOutOfBoundsException: length=2; index=2
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.widget.AbsListView$RecycleBin.addScrapView(AbsListView.java:6739)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.widget.AbsListView.trackMotionScroll(AbsListView.java:5114)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.widget.AbsListView.onGenericMotionEvent(AbsListView.java:3811)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEventInternal(View.java:7801)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7782)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchTransformedGenericPointerEvent(ViewGroup.java:1824)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewGroup.dispatchGenericPointerEvent(ViewGroup.java:1777)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchGenericMotionEvent(View.java:7775)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchGenericMotionEvent(PhoneWindow.java:2076)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at com.android.internal.policy.impl.PhoneWindow.superDispatchGenericMotionEvent(PhoneWindow.java:1525)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.app.Activity.dispatchGenericMotionEvent(Activity.java:2494)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchGenericMotionEvent(PhoneWindow.java:2030)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.View.dispatchPointerEvent(View.java:7888)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:3947)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:3826)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3442)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3411)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3518)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3419)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:3575)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3442)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3411)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3419)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:5532)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:5512)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:5483)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:5612)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:185)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.os.MessageQueue.nativePollOnce(Native Method)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.os.MessageQueue.next(MessageQueue.java:138)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.os.Looper.loop(Looper.java:123)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at android.app.ActivityThread.main(ActivityThread.java:5001)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at java.lang.reflect.Method.invokeNative(Native Method)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at java.lang.reflect.Method.invoke(Method.java:515)
11-28 15:18:16.707: E/MessageQueue-JNI(3155): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java

解决方法:分析错误提示感觉核心要素是由于MessageQuene队列超越边界了,故考虑将Adapter中item类型的数目增大实际只有2种但是设置为3种,发现此bug解决,根本原因不详,还请大神赐教。难道item的类型数目决定了messageQuene的大小?

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
ListViewAndroid 平台上常用的列表控件之一,它可以展示大量的数据,并且支持滚动。当我们往 ListView 中添加大量数据时,可能会出现滚动卡顿等问题,这时就需要进行优化,其中之一就是循环滚动。 循环滚动,即当列表滚动到底部时,继续滑动,列表将从头部开始重新展示数据,从而实现无限滚动的效果。下面介绍一下 ListView 循环滚动的实现方法。 1. 首先,我们需要在 ListViewAdapter 中进行特殊处理,将列表的数据源按照一定的规律进行循环,比如将最后一项数据插入到第一项之前,将第一项数据插入到最后一项之后。 2. 然后,在 ListView滚动监听事件中,当滚动到列表底部时,将列表的滚动位置设置为 0,即回到列表头部,同时更新数据源,将最后一项数据插入到第一项之前,从而实现循环滚动。 下面是一个示例代码: ``` // 在 Adapter 中进行数据源处理 @Override public int getCount() { return dataList.size() + 2; // 数据源长度需要加上两个 } @Override public Object getItem(int position) { if (position == 0) { return dataList.get(dataList.size() - 1); // 最后一项数据插入到第一项之前 } else if (position == getCount() - 1) { return dataList.get(0); // 第一项数据插入到最后一项之后 } else { return dataList.get(position - 1); } } // 在 ListView滚动监听事件中进行循环滚动处理 listView.setOnScrollListener(new AbsListView.OnScrollListener() { @Override public void onScrollStateChanged(AbsListView view, int scrollState) { // 滚动结束时判断是否滚动到底部 if (scrollState == SCROLL_STATE_IDLE && listView.getLastVisiblePosition() == getCount() - 1) { // 将列表的滚动位置设置为 0,即回到列表头部 listView.setSelection(0); // 更新数据源,将最后一项数据插入到第一项之前 dataList.add(0, dataList.get(dataList.size() - 1)); dataList.remove(dataList.size() - 1); adapter.notifyDataSetChanged(); } } }); ``` 以上就是 ListView 循环滚动的实现方法,通过特殊处理数据源和滚动监听事件,可以实现无限滚动的效果,提升用户体验。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值