Databases
StackOverflow2013
Postsdbo
POMemory usage in ListView with dynamic layout data
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMemory usage in ListView with dynamic layout data
    primarykey
    data
    text
    <p>I am working on a custom ListView with nested data for each row. I want to show a person's name with a checkbox for each line, and then dynamically add sub-rows to the ListView for 1-to-many phone numbers associated with that person.</p> <p>That is currently working. However, with larger datasets I am seeing slowdowns and crashes due to intense memory usage. Is there a better way to accomplish what I'm trying to do? </p> <p>Here is an example of what I want to see:</p> <pre><code>[] Joe Smith [] 1-555-444-3333 [] 1-555-777-6655 [] 1-555-234-3232 [] John Doe [] 1-555-882-3434 [] Someone Else [] 1-555-949-0304 [] 1-555-392-4433 </code></pre> <p>Here is the code I'm currently using in the getView() function for my ArrayAdapter. I tried to clean it up some, so if there are any compile errors, they are likely a typo from my cleanup.</p> <pre><code>public View getView(int position, View convertView, ViewGroup parent) { View vi=convertView; ViewHolder holder; CustomContactInfo custom_contact = getItem(position); if(convertView==null){ inflater = (LayoutInflater)getContext().getSystemService(Context.LAYOUT_INFLATER_SERVICE); vi = inflater.inflate(R.layout.name_line, null); holder=new ViewHolder(); holder.contact_name=(TextView)vi.findViewById(R.id.contact_name); holder.cb_selected=(CheckBox)vi.findViewById(R.id.contact_check); holder.phone_numbers=(LinearLayout)vi.findViewById(R.id.phone_number_container); vi.setTag(holder); } else { holder=(ViewHolder)vi.getTag(); } // Set the name of the contact on the main line holder.contact_name.setText(custom_contact.name); // Add the custom views for each phone number holder.phone_numbers.removeAllViews(); for (Phone p : custom_contact.phones) { View v = this.inflater.inflate(R.layout.phone_number, null); CheckBox cb = (CheckBox)v.findViewById(R.id.phone_check); TextView number = (TextView)v.findViewById(R.id.phone_number); number.setText(p.phone_num); holder.phone_numbers.addView(v); } return vi; </code></pre> <p>}</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBlather
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMemory usage in ListView with dynamic layout data
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMemory usage in ListView with dynamic layout data
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI recommend trying not to display so much data within a ListView. I've noticed they are incredibly easy to slow down, even with the EfficientAdapter concept you are using. You can try ExpandableListView, although I don't think it will do much considering it's essentially what you've already created.
      singulars
      1. POMemory usage in ListView with dynamic layout data
      1. USmrres1
    2. COAnother suggestion is to minimize the amount of data actually being drawn in the View. That includes different text colors and so forth. The more detailed the View is, the longer it's going to take to draw on the screen, and the more apt it will be to bog down the scrolling of the list.
      singulars
      1. POMemory usage in ListView with dynamic layout data
      1. USmrres1
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload