[jira] [Commented] (FLEX-33347) DateSpinner dateAndTime jumping

["Fréderic Cox (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLEX-33347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551240#comment-13551240 ] 

Fréderic Cox commented on FLEX-33347:
-------------------------------------

Thanks for this fix! And so quickly! I notice you set the month twice now. Is that for a specific reason?

newDate.month = spinnerDate.month;
                         newDate.date = spinnerDate.date;
                        newDate.month = spinnerDate.month;
                
> DateSpinner dateAndTime jumping
> -------------------------------
>
>                 Key: FLEX-33347
>                 URL: https://issues.apache.org/jira/browse/FLEX-33347
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Mobile: DateSpinner
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: Both mobile (iOS) and desktop (Mac) I've tested it
>            Reporter: Fréderic Cox
>            Assignee: Carol Frampton
>             Fix For: Apache Flex 4.10.0
>
>
> As reported on http://stackoverflow.com/questions/9126194/flex-mobile-4-6-datespinner-dateandtime-jumping-from-jan-31st-to-march-1st:
> set the date in DateSpinner to January 30 or 31 (using mouse or touch)
> click (mouse or touch) on February 1 (visible one or two rows below on the DateSpinner)
> The Datespinner does spin forward but does not stop at February 1: it jumps to March 1. The same behavior can be observed with March 31 - mouse click on April 1 causes a jump to May 1; with May 31 - mouse click on June 1 jumping to July 1, and so on.
> I suspect this behavior is related to the fact that the next month has less days than the prior month (30 instead of 31, or 29 in the case of February 2012), but it is not the behavior that I would like to see when following these two steps. Does anyone know a workaround or fix?
> When the DateSpinner is set with displayMode as 'date' all is well, but that doesn't work in my use case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira