Thank you for reporting this bug. We will make it our priority to review this report.
-
Ext User
[FIXED] Why does Carousel have touchend and scrollend handlers for its scroller?
The scrollend handler uses the Carousel's next() and previous(), but the touchend handler just adds or subtracts the width and calls scrollTo directly. Addtionally, the touchend handler has a magic number for a drag threshold -- one that I would like to adjust, actually, because currently just about *any* drag movement (3 pixels, it seems by the magic number) results in a rotation of the carousel. This leads leads to accidental rotation. Couldn't the touchend handler be dropped?
Anyways: The best example is swiping through pages in the iPhone home screen. Drag a page of apps across the screen (past halfway) and then ever-so-slightly flick back towards your starting point and it returns to where you began. It feels very natural.
-
-
Ext User
Carousel now seems broken with v0.91.
The indicator shows that it's switching panes, but the content just snaps back to the first pane! Ideas?
-
-
-
Ext User
My replies to this thread have been lost a couple times today: Mine was a false alarm. I just hadn't copied the new CSS over from the release.
One related item: Can the delta for switching panes become configurable? It's currently hardcoded to 3 pixels. I'd like it to be 50% of width. (Additionally, there ought to be different behavior for dragging and releasing -- handled by the current onTouchEnd -- and "flicking". The model is the iPhone springboard: A quick flick from anywhere switches pages as does touch-dragging the page past the midpoint and releasing. But they *are* separate gestures.
-