0 Replies Latest reply on Nov 9, 2009 3:32 PM by kevinklin

    [svn:fx-trunk] 11586: Fix for Range-based components to behave like the MX Slider instead of the MX NumericStepper .

    kevinklin Adobe Employee

      Revision: 11586

      Author:   klin@adobe.com

      Date:     2009-11-09 13:51:48 -0800 (Mon, 09 Nov 2009)


      Log Message:


      Fix for Range-based components to behave like the MX Slider instead of the MX NumericStepper. Also, snapInterval now defaults to stepSize if snapInterval is not explicitly set. Various fixes for wireframe skins.


      Range.as - Valid values are now increments of snapInterval starting from the minimum value, but are still constrained by the maximum. The maximum is still included in the range. For example, a Slider with min=1, max=10, and snapInterval=2 has a range of . I modified nearestValidValue() to take the minimum into account when calculating the nearest value. Also, added logic to have snapInterval default to stepSize if stepSize is explicitly set and snapInterval is not. Edited ASDocs to reflect these changes.


      Spinner.as, NumericStepper.as - Edited ASDocs to reflect the Range changes.


      CheckBoxSkin.mxml, RadioButtonSkin.mxml - Added focusSkinExclusions() for the labelDisplay.


      HSliderSkin.mxml, VSliderSkin.mxml - Added dataTip.


      QE notes: No

      Doc notes: No

      Bugs: SDK-23264, SDK-23602, SDK-23903, SDK-23907

      Reviewer: Hans

      Tests run: checkintests, Slider, NumericStepper, ScrollBar

      Is noteworthy for integration: No


      Ticket Links:







      Modified Paths:







          flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/RadioButtonSkin.mx ml