devstudent wrote: > I don't understand the significance of this. Why should it matter what > order it's called in? getView is called with the position that the > returned View will occupy. If getView with position N-1 is called > first, the View that it returns (e.g. the loading... row) will still > be displayed at the end of the list view.
That was why I was inquiring about his comment. I do not understand the significance of the sequence either. As you describe, I am relying upon putting the "loading..." view in the N-1th slot, then changing that view to be something else once the loading is complete. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android 1.5 Programming Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
