Ooops...nevermind...still Hosed. Any advice appreciated (Seekbar now has a mind of it's own)
On Sat, Mar 10, 2012 at 11:18 PM, JJ B <[email protected]> wrote: > Hello, > > I think I figured this one out. > > Of course, I re-watched Romain Guy's IO presentation on ListViews and now > I understand it a lot more. Even though my list will not be larger than 60 > rows, I am assuming that "re-using the convertView" will help my memory > issues a bit. > > With regard to my initial issue, I found the android: listview XML > attribute to persist the position of the Progress value so this seems to be > working. > > Please let me know if there are any other suggestions to watch out for > with regard to Seekbar widget use within a listview row. > > Thanks, > > JJ > > > On Sat, Mar 10, 2012 at 1:30 PM, JJ B <[email protected]> wrote: > >> Hello, >> >> I have an app with a list of SeekBar widgets generated within a ListView. >> When the list is relatively long, the Progress values reset themselves to >> their default position after being set by the user. (the list can be as >> long as 50 to 60 rows). >> >> DDMS gives me the following suspicious output lines: >> >> "Forcing collection of SoftReferences for 532496-byte allocation" >> >> "GC_Before_OOM freed 0k, 5% free 62762k/65415k, paused 56ms" >> >> "Out of memory on a 532496-byte allocation" >> >> May this be a function of the device? (I used the Galaxy Tab 10.1 to >> debug), the SeekBar background graphic? (8kb 9-patch .png back with 100kb >> .png thumb) or the two EditText views in each row? (each row has a SeekBar >> and two EditText views). >> >> Many Thanks, >> >> JJ >> >> >> > -- 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
