Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, I think you should be aware of this: <a href="https://stackoverflow.com/questions/4490821/scrollview-inside-scrollview">ScrollView Inside ScrollView</a></p> <p>In short: <strong>using scrollviews inside scrollviews is a bad thing that breaks many optimizations.</strong></p> <p>Now, onto your question.</p> <p>I've had a similar need to what you described. I ended up implementing a custom view and its <code>onDraw</code> method. This was in part because I was drawing something not trivial and you may not have to do it.</p> <p>Anyway, I believe that your best option is:</p> <ol> <li>Implement a custom view that extends relative layout</li> <li>create the layout of this view with the top, left and "main" views that will be the scrollable components</li> <li>add a <a href="http://developer.android.com/reference/android/view/GestureDetector.OnGestureListener.html" rel="nofollow noreferrer">OnGestureListener</a> to this view and pass touch events in your activity into the custom view</li> <li>when your gesture listener detects a fling or a scroll, invoke <code>scrollBy</code> in each of the scrolling views. When you do this, if you want the top view to scroll horizontally only, pass 0 as the vertical scroll distance.</li> <li>In order to implement smooth fling movements, you need to create a <a href="http://developer.android.com/reference/android/widget/Scroller.html" rel="nofollow noreferrer">scroller</a> (in your custom view). When the gesture listener detects a fling event, set the scroller up. Then, override your custom view's <code>computeScroll()</code> method and update the scroll in each of child views. <strike>Check this <a href="http://androidcore.com/android-programming-tutorials/608-android-two-dimensional-scrollview.html" rel="nofollow noreferrer">example</a> to know how to implement it. I apologize, I will try to post a better example when possible.</strike> <strong>Check my code below... it's simpler :)</strong></li> </ol> <p><strong>Update:</strong> sample code</p> <pre><code>@Override public void computeScroll() { if (scroller.computeScrollOffset()) { if (!scrolledLastFrame) { lastX = scroller.getStartX(); lastY = scroller.getStartY(); } int dx = scroller.getCurrX() - lastX; int dy = scroller.getCurrY() - lastY; lastX = scroller.getCurrX(); lastY = scroller.getCurrY(); doScroll(dx, dy); scrolledLastFrame = true; } else { scrolledLastFrame = false; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAndroid: Synchronized scrolling of two different views
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPedro Loureiro
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid: Synchronized scrolling of two different views
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer. The post you refer to seems to discuss the combination of scroll views with list views though? I do realize that the nesting of scroll views probably isn't optimal, but it seemed like the only alternative that didn't require a new widget from scratch. Before I consider this question answered though, I wonder how this guarantees more "synchronized" scrolling than my current solution? Won't I still have to scroll one view (grid, sticky view) at a time, that may cause a slight offset in how they are scrolled?
      singulars
      1. PO
      1. USAndreas
    2. CONo. I think that your "sync" problem is because when you get the information about the scroll, that has already been processed by one view and then you order the others to scroll alike the first one. This way, one view scrolls and the others will do the corresponding scroll in the next cycle. With my approach, all views scroll at the same time. And you won't have that problem.
      singulars
      1. PO
      1. USPedro Loureiro
 

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