On Feb 20, 2011, at 3:44 AM, Quincey Morris wrote: > For completeness, [...]
In the spirit of completeness, I should mention that because of my particular situation I don't have to think about handling arrow keys or the page up/down keys. The other Andy (the OP) might care about handling these keys given that he's using a table view. > On Feb 20, 2011, at 00:17, Andy Lee wrote: [...] >> I notice WebKit does the expected thing with nested scroll views (for >> example in a typical web mail window in Safari). This includes cases where >> the inner scroll view *can* scroll. I actually find this annoying. In *this* >> case I'd prefer the scroll wheel to stop dead at the top or bottom. It's a >> Fitt's Law kind of thing for me; I want to be able to scroll, scroll, scroll >> to the bottom of a list and not have to be careful about scrolling so much >> that I shift the whole window contents around. But maybe arguments could be >> made the other way. > > I hate that too. And the reverse: sometimes I want to scroll the window but > end up scrolling a text field instead. > > Perhaps the real answer is that nested scrolling views just have *terrible* > usability, period. Could be. I thought of a case where I do want the outer scroll view to scroll: if the inner scroll view is partly outside of the clip view, then I want the outer scroll view to scroll at appropriate times to expose it. What I don't want is for the outer scroll view to *always* scroll when the inner scroll view has reached one of its extremes. > Or perhaps the best that could be done is for scroll views to pass > scrollWheel events up the responder chain *if* there's another scroll view > further up the chain (so that the scroll wheel is handled at the highest > possible level) *except* if the scrollWheel event is directly over a view's > scroll bar, in which case it would be processed by the scroll view that the > scroll bar belongs to. Would that work better? (The discoverability wouldn't > be great, though.) Whatever the logic is, I'd want it to be natural without the user having to realize there is any special-casing at all -- they just do what comes naturally. I do think there might be something to the idea of a scroll view checking whether it has an enclosingScrollView. --Andy _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
