Databases
StackOverflow2013
Postsdbo
POInertial Scrolling & -ScrollWheel: on OS X
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POInertial Scrolling & -ScrollWheel: on OS X
    primarykey
    data
    text
    <p><strong>THE PROBLEM:</strong></p> <p>I have an NSScrollView. I'm using it to implement a custom "Table View" with rows of data that are actually NSViews. (Note: this is not an instance of NSTableView.)</p> <p>As I scroll vertically (there is no horizontal scrolling), I use a boundsChanged notification to add (as subviews of the scrollView's contentView) the NSViews that become visible (the ones with frames that intersect the scrollView's document visible rect) and to remove the ones that are no longer visible (frames outside of the scrollView's visible rect.)</p> <p>The process works wonderfully except when it comes to inertial scrolling. If I have my cursor over cell X and I flick the trackpad to scroll downwards FAST with inertia, cell X quickly leaves the visible rect and, as such, is removed from the scrollView's contentView. BUT, that kills inertial scrolling. If I do NOT remove cell X as a subView, then inertial scrolling works perfectly.</p> <p><strong>WHAT I NEED:</strong></p> <p>A way to keep inertial scrolling while still removing the NSView that the cursor happened to be on top of when the user started the scrolling gesture.</p> <p><strong>WHAT I'VE TRIED:</strong></p> <p>I've looked at NSResponder's method:</p> <pre><code>-scrollWheel:(NSEvent *)theEvent </code></pre> <p>The default implementation passes scrollWheel to the next responder. So, I subclassed NSScrollView and implemented this method to try to stop it from passing the scrollWheel event to the individual subViews inside the scrollView's contentView. Didn't work. </p> <p>So then I went into my NSViews (the ones I'm adding to the contentView) and overrode scrollWheel to pass the event back to the scrollView itself. Didn't work. </p> <p>I still get scrolling in both cases, but not with inertia. </p> <p>Any ideas? Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBryan
    1. USBryan
    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. POInertial Scrolling & -ScrollWheel: on OS X
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POInertial Scrolling & -ScrollWheel: on OS X
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POInertial Scrolling & -ScrollWheel: on OS X
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen you say "implement a standard 'Table View'", do you mean you're using an `NSTableView`?
      singulars
      1. POInertial Scrolling & -ScrollWheel: on OS X
      1. USJosh Caswell
    2. CONo, I mean I'm rolling my own custom "table View." The official NSTableView class is... outdated (to be nice about it.) So I'm creating my own "table view" by simply adding/removing NSViews to a scrollView as the user scrolls.
      singulars
      1. POInertial Scrolling & -ScrollWheel: on OS X
      1. USBryan
    3. COThe way to do this on iOS is to use a delegate, but sadly there's no such delegate for NSScrollview to detect when it stops/starts.
      singulars
      1. POInertial Scrolling & -ScrollWheel: on OS X
      1. USMitchell Currie
 

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