[
https://issues.apache.org/jira/browse/FLEX-27543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-27543:
---------------------------------
Labels: easytest (was: )
> NumericStepper should loop from max to min and min to max buy default.
> ----------------------------------------------------------------------
>
> Key: FLEX-27543
> URL: https://issues.apache.org/jira/browse/FLEX-27543
> Project: Apache Flex
> Issue Type: Improvement
> Components: Spark: NumericStepper
> Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
> Reporter: Adobe JIRA
> Labels: easytest
>
> When a NumericStepper has a minimum and maximum set on it it doesn't give any
> feedback to the user when these values are reached if they are using the
> incrment/decrement buttons or the cursor keys (if they are using the text
> input and add an invalid value, the control update to a valid value and
> therefore isn't unresponsive). Therefore to the user the control just becomes
> unresponsive.
> By default the NumericStepper should loop the values from max to min and min
> to max buy default, and have a Boolean property that can be set to stop this
> default behavior. This means that the control never becomes unresponsive and
> the user can clearly see a max/min is reach when the value loops and make a
> decision on the value they want to use (much like the steppers you see on
> IPhone/IPad.
> http://bugs.adobe.com/jira/browse/SDK-30477 goes some way to resolving the
> unresponsive issue, but doesn't take into account if the user is using their
> cursor keys, therefore looping would be the best default behavior.
--
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
