On Jun 27, 11:44 am, "Romain Guy" <[EMAIL PROTECTED]> wrote: > Why would you do it this way? ListView will already load and display > as many elements as it can. You are just forcing ListView to work in a > way that's it is not meant for and, worse, you are forcing it to work > in a very inefficient way. What exactly are you trying to achieve?
The activity I'm creating has many elements in a ScrollView. The ListView is just one of them. When the ListView gets displayed normally, it loads and displays as many elements as fits on the screen, which turns out to be one or two rows out of maybe 10-20. This creates a very small "visual window" for the ListView, which is unattractive and not functional. What I would want is a view (doesn't have to be ListView, since as you're saying, it wasn't designed that way) which is backed by an Adapter but will load and display all my elements. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
