Flex 2 : Possible bug in Slider

Hi,
I have been trying to restrict the thumbs of an HSlider from
overlapping.
Setting allowThumbOverlap to false did not work.
I noticed that the ability of the thumbs to overlap is
directly related to the maximum value allowed for the slider.
Given below is an example for the same. I presume this must
be a bug, since the documentation mentions
nothing about this. If somebody can throw more light on this,
it would be great.
TestSlider.mxml
===========================
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
xmlns="*">
<mx:HBox>
<mx:Label text="Maximum 13" width="90"/>
<mx:HSlider id="slider13" width="180" thumbCount="2"
snapInterval="1" minimum="0" maximum="13" dataTipPlacement="bottom"
/>
<mx:Label text="Thumbs overlap in both directions"
width="300"/>
</mx:HBox>
<mx:HBox>
<mx:Label text="Maximum 14" width="90"/>
<mx:HSlider id="slider14" width="180" thumbCount="2"
snapInterval="1" minimum="0" maximum="14"
dataTipPlacement="bottom"/>
<mx:Label text="Thumbs overlap from left to right"
width="300"/>
</mx:HBox>
<mx:HBox>
<mx:Label text="Maximum 15" width="90"/>
<mx:HSlider id="slider15" width="180" thumbCount="2"
snapInterval="1" minimum="0" maximum="15"
dataTipPlacement="bottom"/>
<mx:Label text="Thumbs do not overlap" width="300"/>
</mx:HBox>
</mx:Application>
===========================
Regards!
Santosh

Santosh,
This is indeed a bug. Thank you for bringing it to our
attention. As a
workaround, try using different values for the width property
or don't
specify a width at all.
Jason Szeto
Adobe Flex SDK Developer
"stchavan" <[email protected]> wrote in
message
news:e9lh3m$sv0$[email protected]..
> Hi,
>
> I have been trying to restrict the thumbs of an HSlider
from overlapping.
> Setting allowThumbOverlap to false did not work.
> I noticed that the ability of the thumbs to overlap is
directly related to
> the
> maximum value allowed for the slider.
> Given below is an example for the same. I presume this
must be a bug,
> since
> the documentation mentions
> nothing about this. If somebody can throw more light on
this, it would be
> great.
>
> TestSlider.mxml
> ===========================
> <?xml version="1.0" encoding="utf-8"?>
> <mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
xmlns="*">
> <mx:HBox>
> <mx:Label text="Maximum 13" width="90"/>
> <mx:HSlider id="slider13" width="180" thumbCount="2"
snapInterval="1"
> minimum="0" maximum="13" dataTipPlacement="bottom" />
> <mx:Label text="Thumbs overlap in both directions"
width="300"/>
> </mx:HBox>
> <mx:HBox>
> <mx:Label text="Maximum 14" width="90"/>
> <mx:HSlider id="slider14" width="180" thumbCount="2"
snapInterval="1"
> minimum="0" maximum="14" dataTipPlacement="bottom"/>
> <mx:Label text="Thumbs overlap from left to right"
width="300"/>
> </mx:HBox>
> <mx:HBox>
> <mx:Label text="Maximum 15" width="90"/>
> <mx:HSlider id="slider15" width="180" thumbCount="2"
snapInterval="1"
> minimum="0" maximum="15" dataTipPlacement="bottom"/>
> <mx:Label text="Thumbs do not overlap"
width="300"/>
> </mx:HBox>
> </mx:Application>
> ===========================
>
> Regards!
>
> Santosh
>

Similar Messages

  • Possible bug? formatted number 0 displays as  4,294,967,295

    This is really two questions in one. First, I have a routine
    that sometimes provides a result of 0, which is *sometimes*
    displayed in an AdvancedDataGrid column as 4,294,967,295, which I'm
    assuming is somehow a meaningful number (largest int?). Anyway, I
    have an ADG with a column defined as:
    <mx:AdvancedDataGridColumn headerText="Remaining work"
    labelFunction="rem_work_fmt" textAlign="right" />
    The labelFunction called is shown below:
    private function rem_work_fmt(item:Object,
    column:AdvancedDataGridColumn):String
    var num:String =
    numberFormatter.format(item.get_remaining_work());
    trace ("result: " + num);
    return num;
    The trace output prints: "result: 0" as expected, but the
    number displayed in the grid is sometimes 0 and sometimes
    4,294,967,295.
    More weirdness, this only happens to the last column in the
    ADG. I call the same format logic on a different column and have
    never seen the wrong result. Also, the same underlying function
    "get_remaining_work()" is called elsewhere on the same data and the
    result is correctly displayed in a text field as 0.
    Second question, I've run into some other possible bugs,
    which I haven't reported because I found a work around. How does
    one do that in the beta program?

    lw1001,
    Bugs can be filed in the public bug base at
    http://bugs.adobe.com/flex/
    You'll need to sign up before you can submit bugs.
    Also, if you can attach the bug files to the bug report, it
    makes it a lot easier for Adobe to investigate.
    Let me know if you have any further questions/problems.
    Peter

  • [svn:fx-trunk] 9127: Fixes bug in Slider animation where we would set the actual value during the animation , ignoring any snapInterval setting.

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

  • Possible Bug In Apex 4.0.2

    Hi Everyone.
    I would like to report what I think is a bug in Apex 4.0.2.
    If you go to my workspace on apex.oracle.com:
    Workspace = EEG
    Username = [email protected]
    Password = galaxy (all lowercase)
    Run the application: 37796 - Elie_Various_Goodies [no credentials are required]
    This app was imported from my 4.0.1 workspace at my job. On the page I created two Date Picker items, P1_BEGIN_DATE and P1_END_DATE. I set them up so that whenever a user selects a begin date, a dynamic action "MANAGE_DATES" fires and automatically sets P1_END_DATE to this selected begin date value. Now when a user goes to select an end date, the displayed calendar starts at the previously selected begin date rather than the default of "Today".
    All of this worked fine on my office (4.0.1) workspace. However, after exporting this app and then importing onto apex.oracle.com, none of this functionality would work. Even worse, whenever I try to select a begin date or even an end date, the selected dates never make it into the date picker fields. Displaying the "Session" window shows these fields as empty.
    It was only after I copied the two date picker fields and also re-created my dynamic action (P1_BEGIN_DATE2, P1_END_DATE2, MANAGE_DATES) did my functionality return.
    This behavior is quite strange. I can only think this is some sort of bug attributed to the export/import process when exporting a 4.0.1 app into a 4.0.2 workspace. I am not sure if this bizarre behavior happens with non-date picker items. Nor am I sure if this beavior would be repeated if I export/import from 4.0.2 into the another 4.0.2 environment.
    Another strange thing I noticed. If I change my date picker items to be "date picker (classic)" type items, the dynamic action does not work at all. This is true in both 4.0.2 and 4.0.1. I'm not sure if this a bug or not. It could be that the classic date picker is just not "javascript" enabled so to speak. If that is true, then it would have been nice if the docs would have warned us about this.
    Has anyone else seen this behavior?
    Thank you.
    Elie

    Hi Joel.
    First let me thank you for the warning about allowing "everyone" access to my workspace.
    You're correct, of course. Anyone could destroy anything within my workspace. I guess I was too trusting especially as I have seen many posts on the Forum where others have given access to their workspace so that responders can offer help. I really should be more discreet about this. Again, thank you. Needless to say, I have changed my password.
    With respect to the possible bug, the MANAGE_DATES dynamic action is intended to be a submit page because that is the only way I can see to get BOTH the P1_END_DATE date picker item as well as the end date textual field to be assigned the selected P1_BEGIN_DATE. I tried to use a dynamic action in which javascript sets the value of the end date textual field to the selected P1_BEGIN_DATE value. This works without the need to submit the page. Unfortunately, this does not cause the P1_END_DATE date picker item to default to this value. Instead, the default remains at today's date. This is why I finally resorted to a dynamic action that submits the page whenever a new value is selected (that is, a "change" event) from the P1_BEGIN_DATE date picker item.
    All of this works in my office 4.0.1 environment. However, I was puzzled when this fails under 4.0.2 on the hosted web site at apex.oracle.com. This is why I posted a "possible" bug in 4.0.2.
    I hope this all makes sense.
    One more thing, as already mentioned in my original post, this "defaulting a date picker" functionality does NOT work at all for the "classic" date picker items in both 4.0.1 nor in 4.0.2. I realize one can implement this functionality (I' guessing) my using, say, a "onChange" javascript call to submit the page. It's just funny that the "classic" date picker items are not acted upon by the dynamic action MANAGE_DATES that submits the page.
    Thank you.
    Elie

  • Possible bug found in Mac Os X Tiger 10.4.11 in conjuction with iPod Touch

    Dears,
    I think I've found a possible bug in Mac Os X version 10.4.11 in conjunction with iPod Touch.
    When the iPod is connected during boot, my Bluetooth hardware fails to be detected. When I restart the portable without the iPod connected, my Bluetooth hardware is recognised & activated again. It is reproduceable.
    1. Attach iPod Touch before starting the MacBook Pro
    2. Boot the Macbook
    3. Bluetooth hardware should be rendered inoperative
    Restore functionality:
    1. Detach the iPod Touch
    2. Reboot the portable
    3. Bluetooth hardware is restarted / recognised.
    Regards
    Cedric

    wrong category

  • Possible Bug with Drag-and-Drop Being Published via HTML5 - Getting "Undefined" Error When Dragging Object

    Hello,
    I came up with a way to use drag-and-drop interactions that will take advantage of file input so that I may create a drag-and-drop interaction that uses one draggable object over and over allowing multiple scoring/tracking possibilities.  Example use...is having the draggable object be dynamic in that it randomly changes its text so that a learner can drag a term it's possible classification.........thus allowing the possibility of having many terms easily loaded without having to redo a drag-and-drop interaction for each needed terms/classifications updates/changes.
    My Issue: When using a variable to represent the text for a draggable Smart Shape object, I'm getting the error message "undefined" when, clicking/pressing on the object, as well as during the drag of the object. This issue occurs when publishing the project in an HTML5 format.  Flash interestingly enough seems to work perfect...but we are not interested in publishing via Flash any longer.
    To better help you explore this error message, I've set up a test project so that you can see when and how the "undefined" message shows up during a drag-and-drop interaction.  I've also included the Captivate 8 project file used to make the exploration project I'm sharing in this post.
    Link to Captivate project I created for you all to explore "undefined" error message": http://iti.cscc.edu/drag_and_drop_bug/
    Link to this Captivate 8 Project file: http://iti.cscc.edu/drag_and_drop_bug.cptx
    It's pretty interesting how things react in this demo, please try the following actions to see some interesting happenings:
    Drag the Yellow (or variable drag box) to the drag target.
    Drag Black Hello square to Drag target and click undo or reset - watch the undefined message come up on the Yellow (or variable drag box).
    Drag the Yellow (or variable drag box) to the drag target and then use the undo or reset.
    Move both draggable boxes to the drag target and use the undo and reset buttons...
    Anyhow, I know you all are sharp and will run the demo through its paces.
    I'd really be very honored if anyone help me figure out how I could (when publishing out to HTML5) no longer have the "undefined" error message show up when using drag-and-drop with a variable for shape text. This technique has been well received at the college I work at...and I have many future project requests for using such an idea on a variety of similar interactions. I'd love see a solution or see if this might be a bug Adobe may be able to fix!
    I tried to find a solution to the issue documented here for quite some time, but I was not able to find anyone with this problem much less attempting the idea I'm sharing in the help request -  save the darn "undefined" message that comes up!
    Many thanks in advance for any help and/or direction that you all may be able to provide,
    Paul

    Hello,
    I just wanted to supply a minor update related to my drag-and-drop question/issue stated above:
    I did another test using Captivate 7, and found that the undefined error (publishing as HTML5) does not appear and the variable data remains visible - except the variable data turns very small and does not honor any font size related settings.
    I did go ahead and submit this to Adobe as a possible bug today.
    Thanks again for any help related to this issue.  If the issued documented above is solved, it will allow many amazing things to be done using Captivate's drag-and-drop for both regular type projects as well as interaction development for iBooks! 
    Matter of fact if this issue gets fixed, I'll publish a Blog entry (or video) on way's I've used Captivate's drag-and-drop to create dynamic learning activities for Higher Ed. and for use in iBooks.
    ~ Paul

  • Possible bug: Saving array with extended and double precision to spreadshee​t

    If one concatenates a double precision array and an extended precision array with the "build array" vi and then saves using "Write to Spreadsheet File" vi any digits to the right of the decimal place are set to zero in the saved file. This happens regardless of the format signifier input (e.g. %.10f) to the  "Write to Spreadsheet File" vi.
    I am on Vista Ultimate 32 bit and labview 9.0
    This is a possible bug that is easily circumvented by converting to one type before combining arrar to a spreadsheet. Nonetheless, it is a bug and it cost me some time.
    Solved!
    Go to Solution.
    Attachments:
    Spreadsheet save bug.vi ‏9 KB

    Hi JL,
    no, it's not a bug - it's a feature
    Well, if you would look more closely you would recognize the "Save to Spreadsheet" as polymorphic VI. As this polymorphic VI doesn't support EXT numbers internally (it only supports DBL, I64 and String) LabVIEW chooses the instance with most accuracy: I64 (I64 has 64 bits precision, DBL only 53...). So your options are:
    - set the instance to use as DBL (by right-click and "Select type...")
    - make a copy of this VI, save it with a different name and make it support EXT numbers (don't rework the polymorphic VI as you would break compatibility with other LV installations or future revisions)
    And yes, those coercion dots always signal some conversions - you should atleast check what's going on there...
    Message Edited by GerdW on 05-21-2010 10:01 PM
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • [svn] 4612: Flex SDK Bug Fix - Added scaleGrid support to BitmapGraphic

    Revision: 4612
    Author: [email protected]
    Date: 2009-01-21 16:58:51 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Flex SDK Bug Fix - Added scaleGrid support to BitmapGraphic
    SDK-17289 - BitmapGraphic source embed does not respect scale9 grid when scaling
    BitmapGraphic will use the scaleGrid properties defined on its embedded source. Since the Player doesn't support scaleGrid on bitmaps, we have to slice the bitmap into nine sections and then scale/translate each section. We create two arrays of points along the grid. These are used to define the topLeft and bottomRight corners of the section. Based on the internal scaleFactor and which section we are in, we draw a scaled and translated section according to the scaleGrid rules.
    More details:
    - Changed BitmapGraphic to no longer use the BitmapFill to draw. Instead, BitmapGraphic performs the drawing code itself.
    - When the source is set, check if it has scaleGrid properties and store these in internal variable
    - Cache the creation of the 16 grid points array. Flush the cache if the source or dimensions have changed
    - To see this behavior in action, set width/height to different values than the source's natural dimensions and set resizeMode = "scale"
    QE Notes: Add tests for BitmapGraphic with embedded assets using scaleGrid
    Doc Notes: Add docs for this functionality
    Bugs: SDK-17289
    Reviewer: Glenn
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17289
    http://bugs.adobe.com/jira/browse/SDK-17289
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/BitmapGraphic.as

  • [svn:fx-trunk] 5224: Flex SDK Bug Fixes

    Revision: 5224
    Author: [email protected]
    Date: 2009-03-10 14:06:53 -0700 (Tue, 10 Mar 2009)
    Log Message:
    Flex SDK Bug Fixes
    SDK-19772 Initially invisible graphic element can not be made visible
    When visible is false, we were both setting the displayObject invisible and not drawing the graphics. When visible was then set to true, we changed the displayObject visibility, but didn't draw the graphics. The fix is to always draw the graphics when we are not sharing our displayObject. This way we simply toggle visibility on the displayObject on/off, instead of having to perform a redraw.
    SDK-19581 BitmapFill incorrectly handle source property
    Updated code to match code in BitmapGraphic. If the source is a class, we still need to check the type of the newly instantiated instance of that class.
    SDK-19085 unexpected behaviour when setting scaleX < 3 on a LinearGradient
    Internally, we no longer allow scaleX to be less than 2. Visually, this shouldn't have much impact.
    QE Notes: n/a
    Doc Notes: n/a
    Bugs: SDK-19772, SDK-19581, SDK-19085
    Reviewer: Evtim, Chet
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19772
    http://bugs.adobe.com/jira/browse/SDK-19581
    http://bugs.adobe.com/jira/browse/SDK-19085
    http://bugs.adobe.com/jira/browse/SDK-19772
    http://bugs.adobe.com/jira/browse/SDK-19581
    http://bugs.adobe.com/jira/browse/SDK-19085
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/BitmapGraphic.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/baseClasses/GraphicElement.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/BitmapFill.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/LinearGradient.as

    error dateField not selecion date 27/11/2002 ?
    This is bug flex 3 ?
    thanks

  • A possible *bug* in java jcombobox

    Hi all,
    I think i found a possible bug in java jcombobox .. i am sure some of you must have already experienced it..
    supposedly you put a jcombobox in a jpanel
    returned the panel from a method to a calling method..
    and that method adds it to another panel that it had created to a frame..
    and if this happens dynamicaly at runtime, as only after u click a button..
    meaning : without adding the combobox or the immediate parent panelto the contentpane .. directly..
    Then,
    your combox's keylistener may not catch events fired.
    .. this has happened to me many times.. and always i could only find a way out
    .. by adding the combobox to panel that is loaded during startup itself and is
    .. not returned through a method call.
    Your opinions please ?
    'Harish.

    All components in a UI are created at run-time.
    When you create your JFrame you call pack() to align and resize the UI. This validates all the components, and sets the default focus on what ever component should have the focus at start up.
    When you create components and add them as children of another component you have to validate the child and parent. This can be done by calling JComponent.validate()
    As for keylisteners not getting called, this might be fixed if you call grabFocus on the new combobox. I can't see a reason why any listener would stop working.
    For me to really understand what your talking about. I'd need to see source code reproducing this problem.

  • Can someone confirm a possible bug with Universal Access?

    Can someone confirm a possible bug with Universal Access?
    I have a Mac Pro 3,1, 10.7.1 but if you could confirm or not this possible bug with any model.
    In Energy Saver preference pane:
    Set Mac to never sleep.
    Set Display Sleep to ~2 minutes.
    In Desktop & Screen Saver:
    Set screen saver to start at ~1 minutes.
    In Universal Access:
    Check Enable access for assistive devices.
    Check radio button Zoom to On.
    Zoom in window not checked.
    Confirm that Zoom works by pressing:
    ⌥⌘= (option, command, =).
    Set screen back to normal by pressing ⌥⌘-.
    Let screen sleep after screen saver starts.
    Wake screen and see if ⌥⌘= still works.
    Thanks … Ken

    Other than the time intervals (smallest Screen Saver kick-in is 3 minutes), it works fine for me - at least I can still zoom in/out after waking the display.
    Tested on two different MacBook Pro models in 10.7.1

  • Is it possible to do slides in portrait format and fill full page?

    Is it possible to do slides in portrait format and fill full page?

    Are you talking about projecting onto a screen or printing out?
    If you're talking about projection, first, you can't display slides in portrait format, as all slides in a presentation are landscape by default. I believe most all presentation projectors are also landscape only (you'd have to turn it sideways in order to project portrait.
    Second, you can put a portrait picture in the middle of the landscape formatted slide, but there will be a lot of background showing. You could stretch the image to fill the screen, but that would distort it badly or cut off huge parts of it.
    Because of these limitations, you can't have a portrait image fill a landscape slide and fill the full slide.

  • What are the changes / enhancements / or possible bugs in LR 5 Auto Tone

    Can anyone explain what, if any, changes, enhancements, or possible bugs were introduced in the functionality of Auto Tone since LR ver. 5.0. The reason I ask is that I get different results for the Exposure and Contrast adjustments when applying Auto Tone (using ver. 5.3) from the results  (using ver.5.0) shown in the book "Adobe Photoshop Lightroom 5 CIB" in the "Using Quick Develop in the Library module" section, step 4 on page 37. (This difference in results between LR versions was confirmed by the authors of LR5CIB.)

    I'm not sure about any new bugs but the radical exposure mis-calculations have been improved. I had photos that were over exposed to 5 (and even 10, believe it or not) that were exposed to a more appropriate 2 or so following the improvements (in Lr5.2 if memory serves). It's also less likely to radically underexpose.
    Enjoy, (in my opinion, it's much better)
    I think there may have even been further improvement in Lr5.3 but I can't swear to it - seems to preserve a little more contrast than in 5.2 - could be my imagination..
    Rob

  • [svn] 4624: Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements

    Revision: 4624
    Author: [email protected]
    Date: 2009-01-22 13:15:17 -0800 (Thu, 22 Jan 2009)
    Log Message:
    Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements
    SDK-17362 - GraphicElement.getBitmapData doesn't handle 3D transforms
    Added in support to take a bitmap snapshot of a 3D transformed GraphicElement.
    Added a flag to getBitmapData to return a bitmap of the target either in the local or global coordinate space.
    Also, fixed a bug in the bitmap snapshot logic for a 2D GraphicElement that was sharing its displayObject.
    Note that the 3D snapshot isn't accurate if you have set maintainProjectionCenter on an ancestor. There are also limitations when rotation is applied. In addition, getting a local 3D snapshot isn't too accurate once you start scaling ancestors.
    QE Notes: Add mustella tests for getBitmapData
    Doc Notes: Document that getBitmapData now supports 3D transforms
    Bugs: SDK-17362
    Reviewer: Evtim
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17362
    http://bugs.adobe.com/jira/browse/SDK-17362
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

    FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

  • [svn:fx-3.x] 5687: Flex Framework Bug Fix

    Revision: 5687
    Author: [email protected]
    Date: 2009-03-27 16:27:38 -0700 (Fri, 27 Mar 2009)
    Log Message:
    Flex Framework Bug Fix
    SDK-14684 Un-hardcode the 10 digit limit in PhoneNumberValidator
    Added a minDigits property to PhoneNumberValidator. Added new resource string to Validator.properties.
    SDK-16679 NumberValidator.domain should use constants instead of strings
    Added new class NumberValidatorDomainType. Updated the ASDoc and one of the equality checks in NumberValidator.
    QE Notes: add tests for the new minDigits property
    Doc Notes: add documentation for the new minDigits property and NumberValidatorDomainType class
    Bugs: SDK-14684, SDK-16679
    Reviewer: Hans
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-14684
    http://bugs.adobe.com/jira/browse/SDK-16679
    http://bugs.adobe.com/jira/browse/SDK-14684
    http://bugs.adobe.com/jira/browse/SDK-16679
    Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/bundles/en_US/src/validators.properti es
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/NumberValidator.as
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/PhoneNumberValidato r.as
    Added Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/NumberValidatorDoma inType.as

Maybe you are looking for

  • How do I add indication to a cluster

    I have a couple of radio buttons in a cluster and I'd like to add indication to the individual buttons within the cluster.  How is this done?

  • Valuation Type Issue with STOs

    Hello Folks !! In the client environment Materials are going to be Batch Managed as well as Split Valuated (by Country of Origin "H" Category). When we create STOs, Valuation Type of the receiving plant is mandatory and it has to be specified up in t

  • Cost stored in tables MEK3 ,ME13 AND VK13

    Hi All Can you please give me the tables and fields for the cost stored in t-CODES MEK3 ,ME13 AND VK13 regards sandeep kumar

  • Error connecting MDM system from XI through Java proxies-standard component

    Dear Friends We are trying to connect to the MDM system from XI through Java proxies(i.e standard components),in relation to that we have done the following: 1)registered the interfaces a)http://XIserver:port/ProxyServer/register?ns=http://sap.com/xi

  • Adding osuser to a trigger

    I have a trigger on a table which fires after an update on a specific field. I need to get the osuser (NOT the user) who ran the update . Is that possible ?