You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flex.apache.org by "Jan F. Weber (JIRA)" <ji...@apache.org> on 2015/02/12 13:13:11 UTC

[jira] [Created] (FLEX-34749) DateSpinner and SpinnerList scrolling behavior inaccurate/broken

Jan F. Weber created FLEX-34749:
-----------------------------------

             Summary: DateSpinner and SpinnerList scrolling behavior inaccurate/broken
                 Key: FLEX-34749
                 URL: https://issues.apache.org/jira/browse/FLEX-34749
             Project: Apache Flex
          Issue Type: Bug
          Components: Mobile: DateSpinner, Mobile: SpinnerList
    Affects Versions: Apache Flex 4.12.1, Apache Flex 4.13.0, Apache Flex 4.14.0
         Environment: Windows 7 64Bit, Flex 4.14.0, AIR 16
            Reporter: Jan F. Weber
            Priority: Blocker


The scrolling behavior of the DateSpinner and SpinnerList is very inaccurate/broken and does not correctly snap to the nearest list entry after the user has finished scrolling. This happens in most of the use cases. In fact, the lists spin up or down approximately between 3 to 10 entries, depending on the scroll direction.

This seems to be an issue with the throw velocity, which obviously is miscalculated. The effect occurs especially when the mouse or touch-release happens outside of the components bounds. Waiting a few seconds after spinning before releasing does not make any difference.

You can use this example to see the inaccuracy/spinning afterwards after releasing in action:
http://devgirl.org/2011/11/17/flex-mobile-development-datespinner-sample-with-source/




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)