On Mon, Jan 31, 2011 at 12:01, Tomeu Vizoso <[email protected]> wrote: > Hi, > > continuing with this topic, I would like to propose making > MxKineticScrollView's event handling a bit more complicated by letting > pass button and motion events through to its child if the slide > gesture doesn't start in a direction for which we are scrolling.
Just letting people know that the plan right now is to add a scroll-policy property to MxKineticScrollView (just like MxScrollView has) and let all events pass-through (in capture mode) until the threshold has been reached in the direction specified by scroll-policy. I guess that this won't make Mx 1.2 because it's already in API freeze but I would like to hear from a maintainer confirming this. Regards, Tomeu > This means for example that if the horizontal adjustment's dimensions > are such that doesn't overflow the allocated box dimensions, and the > motion events we are getting indicate that the slide is starting > closer to the X axis than the Y axis, we would: > > - abort the scroll operation, > - replay the button press event to its child, > - replay the last(s) motion event to its child. > > I have some confidence that this change wouldn't complicate > MxKineticScrollView much further, I'm only a bit unsure of the > replaying events bit of it. Maybe we would end up needing to duplicate > something like emit_event() in clutter-main.c so moving that to some > new public API may be convenient. > > Thanks, > > Tomeu > _______________________________________________ clutter-app-devel-list mailing list [email protected] http://lists.clutter-project.org/listinfo/clutter-app-devel-list
