[svn:fx-trunk] 14199: ToolTip border skin bug fix

Revision: 14199
Revision: 14199
Author:   [email protected]
Date:     2010-02-16 13:59:53 -0800 (Tue, 16 Feb 2010)
Log Message:
ToolTip border skin bug fix
http://bugs.adobe.com/jira/browse/SDK-24282 - SliderDataTip instantiates it?\226?\128?\153s border class before it?\226?\128?\153s style can be set by Slider
Modified a patch submission to follow the pattern in TextInput. When the borderSkin style changes, the border was not recreated with the new border class.
Thanks go to David Spanton for the original submission
QE notes: yes, need tests for this use case
Doc notes: n/a
Bugs: SDK-24282
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24282
    http://bugs.adobe.com/jira/browse/SDK-24282
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/ToolTip.as

Similar Messages

  • [svn:fx-trunk] 5170: Round 2 of bug fixes for the Spark skins for Halo components.

    Revision: 5170
    Author: [email protected]
    Date: 2009-03-04 17:50:32 -0800 (Wed, 04 Mar 2009)
    Log Message:
    Round 2 of bug fixes for the Spark skins for Halo components. Thanks to Alex for help with the data grid issues.
    Bugs fixed:
    SDK-19655 - Setting rowCount property on DataGrid causes extra blank row to be displayed
    SDK-19652 - Items in a DataGrid do not line up after scrolling.
    SDK-19605 - disabled Halo ColorPicker with Gumbo skin draws too dark
    SDK-19596 - When you have a single button on an Alert, the left edge looks flatter than the right
    SDK-19585 - Menus compiled with the halo theme in Flex 4 have a different backgroundColor than in Flex 3
    SDK-19665 - Halo List with Gumbo skin doesnt draw the alternating item color all the way to the right edge of the control if VScrollBar is present
    SDK-19651 - odd header rendering issue on Halo DataGrid with Gumbo skin
    QA Notes: The alert layout code was positioning the buttons/text on sub-pixel boundaries if the width or height of the alert was an odd number of pixels. We always snap to pixel boundaries now, but this may cause bitmap compare issues with Alert.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19655
    http://bugs.adobe.com/jira/browse/SDK-19652
    http://bugs.adobe.com/jira/browse/SDK-19605
    http://bugs.adobe.com/jira/browse/SDK-19596
    http://bugs.adobe.com/jira/browse/SDK-19585
    http://bugs.adobe.com/jira/browse/SDK-19665
    http://bugs.adobe.com/jira/browse/SDK-19651
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DataGrid.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/alertClasses/AlertForm.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/ScrollControlBase.as
    flex/sdk/trunk/frameworks/projects/halo/defaults.css
    flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/ColorPickerSkin.mxml

  • [svn:fx-trunk] 5152: First pass of bug fixes for the Spark skins for Halo components.

    Revision: 5152
    Author: [email protected]
    Date: 2009-03-03 13:18:45 -0800 (Tue, 03 Mar 2009)
    Log Message:
    First pass of bug fixes for the Spark skins for Halo components.
    Bugs:
    SDK-19963 - themeColor should not affect rollOverColor or selectionColor in flex 4
    SDK-19654 - Spark skin for the Halo ComboBox dropdown needs a drop shadow
    SDK-19637 - Halo HScrollBar/VScrollBar controls dont render correctly when specifying includeIn states
    SDK-19634 - Halo ProgressBar default size is very different when using Halo vs Gumbo theme
    SDK-19626 - Flicker when toggling enabled property on Halo TabBar control with Gumbo skin
    SDK-19556 - selected Halo CheckBox and RadioButton icons briefly flicker when you roll over them
    SDK-19658 - Halo ComboBox with Gumbo skin has an odd flicker
    Doc/QA Notes: The fix for SDK-19963 includes a compatibility-version check. When compatibility-version < 4, setting themeColor implicitly sets rollOverColor and selectionColor, if they have not been set. When compatibility-version >= 4, you must explicitly set rollOverColor and selectionColor, even when using the Halo theme.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19963
    http://bugs.adobe.com/jira/browse/SDK-19654
    http://bugs.adobe.com/jira/browse/SDK-19637
    http://bugs.adobe.com/jira/browse/SDK-19634
    http://bugs.adobe.com/jira/browse/SDK-19626
    http://bugs.adobe.com/jira/browse/SDK-19556
    http://bugs.adobe.com/jira/browse/SDK-19658
    http://bugs.adobe.com/jira/browse/SDK-19963
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxApplication.as
    flex/sdk/trunk/frameworks/projects/framework/defaults.css
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/Button.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/ComboBase.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Application.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RectangularDropShadow.as
    flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/BorderSkin.mxml
    flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/ProgressBarTrackSkin.mxm l

  • [svn:fx-trunk] 10182: This is a bug fix for DropDownList.

    Revision: 10182
    Author:   [email protected]
    Date:     2009-09-11 16:15:57 -0700 (Fri, 11 Sep 2009)
    Log Message:
    This is a bug fix for DropDownList.  When Label changed from a GraphicElement to a UIC it started blocking the mouse events from the anchorButton inside of a DropDownList.  To fix this, I've just disabled the mouse of the labelDisplay in the DropDownListSkin
    QE notes: -
    Doc notes: -
    Bugs: SDK-23054
    Reviewer: Jason
    Tests run: checkintests, DropDownList
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23054
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DropDownListSkin.mxml
        flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/DropDownListSkin.m xml

  • [svn:fx-trunk] 11574: Drag and Drop - Bug fixes:

    Revision: 11574
    Author:   [email protected]
    Date:     2009-11-09 10:53:35 -0800 (Mon, 09 Nov 2009)
    Log Message:
    Drag and Drop - Bug fixes:
    - Added slight delay before drag-scrolling start.
    - Single selection ctrl+drag fixed.
    - Default drop indicator for List that doesn't have drop indicator specified in its skin. The default DI is specified through the new dropIndicatorSkin List style.
    - Memory leak for the drop indicator dynamic skin part.
    - ListItemDragProxy incorrectly listed in spark-manifest.xml moved to SparkClassess.
    QE notes: None
    Doc notes: None
    Bugs: SDK-24047, SDK-23999, SDK-23871
    Reviewer: Glenn, Deepa
    Tests run: checkintests, mustella (List, ListDragDrop)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24047
        http://bugs.adobe.com/jira/browse/SDK-23999
        http://bugs.adobe.com/jira/browse/SDK-23871
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/defaults.css
        flex/sdk/trunk/frameworks/projects/spark/src/SparkClasses.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/TileLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/DropLocation.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/LayoutBase.as
        flex/sdk/trunk/frameworks/spark-manifest.xml
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/ListDropIndicator.as

    Just found a reference to a work around to the issue by putting the macbook to sleep & waking it.  Worked a treat !
    This makes it usable again.  Which is lucky as I was preparing to see how far I could toss the macbook !
    Suppose I'll need to wait for a patch.

  • [svn:fx-trunk] 11737: ComboBox and DropDownList bug fixes

    Revision: 11737
    Author:   [email protected]
    Date:     2009-11-12 13:25:33 -0800 (Thu, 12 Nov 2009)
    Log Message:
    ComboBox and DropDownList bug fixes
    SDK-23635 - Implement type-ahead in DropDownList
    Added code in DropDownListBase keyDownHandler to listen for letters and change the selection if there is a match. At some point, we should modify findKey and findString (I'll file an ECR for that). For now, I've just overridden findKey and cobbled together the logic from List.findKey and List.findString. In ComboBox, we override findKey to do nothing since ComboBox has its own logic that relies on textInput changes.
    SDK-23859 - DropDownList does not reset caretIndex when selection is cleared
    Fixed this in two places. In ComboBox.keyDownHandlerHelper, we update the caret index when ESC is pressed. In DropDownListBase.dropDownController_closeHandler, we update the caret index if the commit has been canceled (ie. ESC was pressed).
    SDK-24175 - ComboBox does not select an item with ENTER when openOnInput = false
    When the ComboBox was closed and the arrow keys were pressed, the selectedIndex was changed. When ENTER was pressed, it was committing actualProposedSelectedIndex, not selectedIndex. The fix is to override the selectedIndex setter to keep actualProposedSelectedIndex in sync if selectedIndex was changed. Usually it is kept in sync when the dropDown is opened.
    SDK-24174 - ComboBox does not scroll correctly when openOnInput = false
    When typing in a match, the caretIndex was changed, but not the selectedIndex (because matching when it is closed doesn't commit the value until you press ENTER or lose focus). When closed, the navigation keys were changing the selectedIndex relative to the previous selectedIndex. I updated this to change relative to caretIndex instead. In most cases, caretIndex and selectedIndex are equivalent while the dropDown is closed.
    Other changes:
    - Replaced some calls to dropDownController.isOpen with isDropDownOpen.
    - Added protection RTE protection to ComboBox.changeHighlightedSelection
    QE notes: None
    Doc notes: None
    Bugs: SDK-23635, SDK-23859, SDK-24175, SDK-24174
    Reviewer: Deepa
    Tests run: ComboBox, DropDownList
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23635
        http://bugs.adobe.com/jira/browse/SDK-23859
        http://bugs.adobe.com/jira/browse/SDK-24175
        http://bugs.adobe.com/jira/browse/SDK-24174
        http://bugs.adobe.com/jira/browse/SDK-23635
        http://bugs.adobe.com/jira/browse/SDK-23859
        http://bugs.adobe.com/jira/browse/SDK-24175
        http://bugs.adobe.com/jira/browse/SDK-24174
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ComboBox.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DropDownListBase.as

    This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
    The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
    Please could you attach DropDow nList.as that you edited ?
    Thank you so much.

  • [svn:fx-trunk] 8520: BitmapFill and BitmapImage bug fixes

    Revision: 8520
    Author:   [email protected]
    Date:     2009-07-10 16:53:09 -0700 (Fri, 10 Jul 2009)
    Log Message:
    BitmapFill and BitmapImage bug fixes
    http://bugs.adobe.com/jira/browse/SDK-17477 - only edge pixels expand when resize this bitmapGraphic
    If repeat mode is false, the Player will extend the edge pixels of the bitmap to fill the empty space. The fix is to limit the fill area to the size of the bitmap.
    http://bugs.adobe.com/jira/browse/SDK-21980 - BitmapFill repeat property behaves differently than BitmapImage
    If repeat mode is false, the Player will extend the edge pixels of the bitmap to fill the empty space. The fix is to draw the transformed bitmapData into a new bitmapData that is two pixels wider and taller than the source bitmap if repeat is false. There is a caching mechanism that keeps the new bitmapData around unless the source, one of the transform properties or the bounds size have changed.
    There is an additional optimization which only uses the extra bitmapData if it is larger than the bounds or if it has been transformed.
    Unfortunately this means that the BitmapFill will keep around an extra bitmapData object in certain circumstances. This situation will most frequently happen when the bitmap is smaller than the shape being filled and repeat is set to false.
    QE Notes: Add tests where the BitmapFill shape or BitmapImage size is larger than the bitmap itself and repeat = false
    Doc Notes: None
    Bugs: SDK-17477, SDK-21980
    Reviewer: Glenn
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-17477
        http://bugs.adobe.com/jira/browse/SDK-21980
        http://bugs.adobe.com/jira/browse/SDK-17477
        http://bugs.adobe.com/jira/browse/SDK-21980
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/BitmapFill.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/BitmapImage.as

  • [svn:fx-trunk] 12816: VideoPlayer full screen bug fix

    Revision: 12816
    Revision: 12816
    Author:   [email protected]
    Date:     2009-12-10 16:19:26 -0800 (Thu, 10 Dec 2009)
    Log Message:
    VideoPlayer full screen bug fix
    SDK-24308 - Full-screen VideoPlayer running as AIR application on dual monitor setup has white background
    If we are running on the AIR Player, then use the Screen bounds API instead.
    QE notes: None
    Doc notes: None
    Bugs: SDK-24308
    Reviewer: Ryan
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24308
        http://bugs.adobe.com/jira/browse/SDK-24308
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as

  • [svn:fx-trunk] 8306: * A trio of compiler fixes.

    Revision: 8306
    Author:   [email protected]
    Date:     2009-06-26 08:05:34 -0700 (Fri, 26 Jun 2009)
    Log Message:
    A trio of compiler fixes.
    tests Passed: checkintests
    Needs QA: YES, please confirm each of the bug fixes with AST
              generation on and off.
    Needs DOC: NO
    Bug fixes: SDK-20158, SDK-21871 with AST generation, SDK-21528
    API Change: NO
    Reviewer: Pete F.
    Cycloner: Gaurav
    Code-level description of changes:
      as3/AbstractSyntaxTreeUtil.java
        Modified generateMemberExpression() to handle expressions like Vector..
      as3/binding/DataBindingFirstPassEvaluator.java
        Renamed isString() to isArrayOrString() and added check for Array.
      mxml/lang/StandardDefs.java
        Added intern() to PACKAGE_FLASH_UTILS, because it's used in AST
        generation now.
      mxml/lang/ChildNodeHandler.java
        Modified invoke() to call defaultPropertyElement() even in the
        case of binding expressions.
      mxml/builder/ComponentBuilder.java
        Modified constructor to initialize bindingHandler.
        Added ComponentDeclarationBindingHandler inner class.
      mxml/builder/DocumentBuilder.java
        Removed ComponentDeclarationBindingHandler inner class.
      mxml/rep/init/ValueInitializer.java
        Modified formatExpr() to handle fully qualified class names when
        the targetType is functionType.
      mxml/gen/ClassDefLib.vm
        Added special case handling, equivalent to compile time singleton
        coercion, for binding source functions when the return type is
        Array.
      mxml/ImplementationGenerator.java
        AST generation equivalent to ClassDefLib.vm changes.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-20158
        http://bugs.adobe.com/jira/browse/SDK-21871
        http://bugs.adobe.com/jira/browse/SDK-21528
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingFirstPassE valuator.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/TypeAnalyzer.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/gen/ClassDefLib.vm
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/ChildNodeHandler.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitializer.ja va

  • [svn:osmf:] 11199: Sample clean up and bug fixing.

    Revision: 11199
    Author:   [email protected]
    Date:     2009-10-27 13:56:22 -0700 (Tue, 27 Oct 2009)
    Log Message:
    Sample clean up and bug fixing.
    Modified Paths:
        osmf/trunk/apps/samples/framework/CuePointSample/src/CuePointSample.mxml

    At least in the version I was using it was, quite literally. Horrible.
    Invalid, unsemantic, not cross-browser, and subject to quirks mode rendering.
    That isn't necessarily a comment on the developers of the system as a whole.  Just those who created the HTML and JS.  And, who knows, perhaps was improved in later versions.
    From my experience with other CMS systems, though, there is sufficient abstraction to fix much of this, if the templates for the HTML and JS can be located.
    I'm hoping that SAP is the same, that there are places to look for the HTML that creates major UI components.
    This seems useful anyway, since customising is more effective if the templates themselves can be changed at that level.
    This also carries over to the IDE - where the sample apps that could be created also generated invalid or unsemantic HTML and JavaScript in my tests. (setting aside my killing my server in my first test of field submission just by pasting a few kilobytes of text in the field )
    Anyway, certainly front-end is not a comment on system as a whole, but lightweight and valid HTML makes styling much easier, so if I could figure out how to fix that, it'd be lovely.
    P.S. - this forum itself uses "color: windowText" for text areas without setting background-color: window.
    Kind of sloppy, easily fixed on my side (where I use a dark UI theme) by overriding the site style.

  • [svn] 3543: Asc front end performance improvements & bug fixes

    Revision: 3543
    Author: [email protected]
    Date: 2008-10-09 11:54:47 -0700 (Thu, 09 Oct 2008)
    Log Message:
    Asc front end performance improvements & bug fixes
    This set of Asc parser/scanner/inputbuffer updates contains changes that simplify the parser?\226?\128?\153s lookahead/match fsm.
    A method, ?\226?\128?\152shift()?\226?\128?\153 has been added that replaces match, when the token to be consumed is known.
    Also, a simplified version of lookahead has been added that returns the lookahead token, which allows use of switch code when the lookahead set is large.
    Simple inputbuffer changes (switching to a String, so that we can use substring instead of valueof) seem to result in about a 2% performance improvement.
    Fixes for:
    ASC-3519
    ASC-2292
    ASC-3545
    All being overlapping bugs related to regexp recognition in slightly differing contexts.
    QA: Yes
    Doc:
    Tests: checkintests, Performance tests, tamarin, asc-tests, mx-unit
    Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3519
    http://bugs.adobe.com/jira/browse/ASC-2292
    http://bugs.adobe.com/jira/browse/ASC-3545
    Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3519
    http://bugs.adobe.com/jira/browse/ASC-2292
    http://bugs.adobe.com/jira/browse/ASC-3545
    http://bugs.adobe.com/jira/browse/ASC-3519
    http://bugs.adobe.com/jira/browse/ASC-2292
    http://bugs.adobe.com/jira/browse/ASC-3545
    Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/InputBuffer.java
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Parser.java
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Scanner.java
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/States.java

    In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
    What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
    Mark

  • [svn:bz-4.0.0_fixes] 20451: backporting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error  : StackOverflowError  We put hard limit to the max object nest level to prevent StackOverFlowError .

    Revision: 20451
    Revision: 20451
    Author:   [email protected]
    Date:     2011-02-24 08:33:31 -0800 (Thu, 24 Feb 2011)
    Log Message:
    backporting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError  We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation.  Checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-570
        http://bugs.adobe.com/jira/browse/BLZ-620
    Modified Paths:
        blazeds/branches/4.0.0_fixes/modules/common/src/flex/messaging/errors.properties
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf0Input.java
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf3Input.java
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • [svn:bz-3.x] 20443: back porting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error  : StackOverflowError  We put hard limit to the max object nest level to prevent StackOverFlowError .

    Revision: 20443
    Revision: 20443
    Author:   [email protected]
    Date:     2011-02-23 21:19:22 -0800 (Wed, 23 Feb 2011)
    Log Message:
    back porting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError  We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation.  Checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-570
        http://bugs.adobe.com/jira/browse/BLZ-620
    Modified Paths:
        blazeds/branches/3.x/modules/common/src/java/flex/messaging/errors.properties
        blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
        blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
        blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf0Input.java
        blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf3Input.java
        blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/AmfIO.java

  • [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

  • [svn:fx-3.x] 8970: Slider Tick bug fix

    Revision: 8970
    Author:   [email protected]
    Date:     2009-07-31 14:03:33 -0700 (Fri, 31 Jul 2009)
    Log Message:
    Slider Tick bug fix
    http://bugs.adobe.com/jira/browse/SDK-15529 - Ticks arent centered properly in HSlider control
    Patch submission from Aaron Whiting:
    "Tick marks drawing code included an x-offset value to adjust the tick mark location by half of the tick line thickness. X-offset value was removed from drawing code and ticks are now centered."
    The ticks no longer need to be offset since we switched from a Sprite symbol to using the drawing API.
    QE notes: Add test case
    Doc notes: None
    Bugs: SDK-15529
    Reviewer: Jason
    Tests run: Slider
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-15529
        http://bugs.adobe.com/jira/browse/SDK-15529
    Modified Paths:
        flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/controls/sliderClasses/Slider. as

Maybe you are looking for