Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From what I can tell, the issue is that your <code>SectionIndexer</code> implementation is unbalanced. Currently you have:</p> <pre><code> public int getPositionForSection(int section) { return _alphaIndexer.get(_sections[section]); } public int getSectionForPosition(int position) { return 0; } public Object[] getSections() { return _sections; } </code></pre> <p>There is a workable implementation telling the list how to determine the position of where a given section begins in <code>getPositionForSection()</code>, but nothing about how to determine which section a given position is located in <code>getSectionForPosition()</code>.</p> <p>When I run a simplified example (on my GTab 10.1 with Android 3.1) using this indexer code I can easily get the scroller handle to go completely off-screen so a user can't get it at all without scrolling all the way to the top of the list. The way to fix this is to balance the indexer by implementing the other method properly:</p> <pre><code> public int getPositionForSection(int section) { return _alphaIndexer.get(_sections[section]); } public int getSectionForPosition(int position) { //Iterate over the sections to find the closest index //that is not greater than the position int closestIndex = 0; int latestDelta = Integer.MAX_VALUE; for(int i=0; i &lt; _sections.length; i++) { int current = _alphaIndexer.get(_sections[i]); if(current == position) { //If position matches an index, return it immediately return i; } else if(current &lt; position) { //Check if this is closer than the last index we inspected int delta = position - current; if(delta &lt; latestDelta) { closestIndex = i; latestDelta = delta; } } } return closestIndex; } public Object[] getSections() { return _sections; } </code></pre> <p>In my example anyway, fixing the <code>SectionIndexer</code> to be more balanced eliminates the issue and the scroll handle never goes below the view. This example code may not work copy/paste for your data source, but it should give you an idea of how to put it into your code.</p> <p>HTH</p>
    singulars
    1. This table or related slice is empty.
    1. POsetFastScrollEnabled don't work perfectly
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDevunwired
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POsetFastScrollEnabled don't work perfectly
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COthanks, thanks very very match
      singulars
      1. PO
      1. UShaythem souissi
    2. COYou are a genius
      singulars
      1. PO
      1. UShaythem souissi
 

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