On Sat, Jan 10, 2009 at 8:05 AM, Mark Murphy <[email protected]>wrote:
> > Faber Fedor wrote: > > Besides, I was guessing that the only reason you put it in the list in > the first place was to have it available to you in the callbacks. You guessed right. > > I'm not quite sure how you're handling a double-click (double-clicks > > aren't that common in Androidland, AFAIK), > > > > I'm not handling it; I just double-click in the emulator and it Just > > Works. Maybe the second click is ignored? I'll test it tomorrow. > > If you're overriding onListItemClick() or something like that, a single > click is all you need. Right again. I think the second-click highlighted the row then the onClickListener kicked in, effectively throwing the second click away. > What has also worked for me is to simply re-point the Cursor (using > movetoPosition()) to the row indicated by the position parameter. Then, > you can grab whatever data you need. I don't know if this works by > design or if future editions of Android will assume the Cursor is > untouched and my changing the position will screw things up. That sounds similar to what I've experienced; when I open a cursor, even if it only one record long, I still have to moveToFirst() before doing any activity with it otherwise things crash. Now, to figure out why I can't update the record... -- Faber Fedor Cloud Computing New Jersey http://cloudcomputingnj.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
