[svn:fx-3.x] 12023: Back-porting a fix for Mike M.

Revision: 12023
Revision: 12023
Author:   [email protected]
Date:     2009-11-19 17:37:22 -0800 (Thu, 19 Nov 2009)
Log Message:
Back-porting a fix for Mike M. for FB-21917 from trunk to get this into 3.5.
QE notes: SDK QE not really, FB QE please test bug scenario on integration.
Doc notes: N/A
Bugs:
FB-21917 - Building project with large number of embedded assets will eventually cause Flex Builder to exit without warning.
Reviewer: Mike M.
Tests run: Checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/FB-21917
    http://bugs.adobe.com/jira/browse/FB-21917
Modified Paths:
    flex/sdk/branches/3.x/modules/swfutils/src/java/flash/swf/SwfEncoder.java

Create a VI with a Waveform Graph on the front panel. On the block diagram, insert a Read From Spreadsheet File function. Connect the All Rows output to the Waveform Graph.
Attachments:
Graph.jpg ‏3 KB

Similar Messages

[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-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] 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] 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:bz-3.x] 20488: backporting BLZ-435 fix for AMFX serialization from BLAZEDS trunk to blazeds 3 .x

Revision: 20488
Revision: 20488
Author:   [email protected]
Date:     2011-02-28 11:52:50 -0800 (Mon, 28 Feb 2011)
Log Message:
backporting BLZ-435 fix for AMFX serialization from BLAZEDS trunk to blazeds 3.x
checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-435
Modified Paths:
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amfx/AmfxInput.java

[svn:bz-4.0.0_fixes] 22605: backporting bug fix for 2956421 lexClient to expose EndpointQueue

Revision: 22605
Revision: 22605
Author:   [email protected]
Date:     2011-09-16 08:14:47 -0700 (Fri, 16 Sep 2011)
Log Message:
backporting bug fix for 2956421 lexClient to expose EndpointQueue
exposing a new API FlexClient.getEndpointQueue(String endpointQueueId)
checkintest not run
tests: YES
@watson: 2956421
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/client/FlexClient.java

[svn:fx-trunk] 9985: * Recommitting revision 9936 with fix for AtEmbed. equals().

Revision: 9985
Author:   [email protected]
Date:     2009-09-03 08:21:37 -0700 (Thu, 03 Sep 2009)
Log Message:
Recommitting revision 9936 with fix for AtEmbed.equals().
Tests run: checkintests
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flash/css/StyleProperty.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/AtEmbed.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:fx-3.x] 5820: Merged (back ported) trunk revisions 4460,4492,4516,4520 ,4585,4630,4692,4726,4964 - 3.x

Revision: 5820
Author: [email protected]
Date: 2009-03-31 13:40:12 -0700 (Tue, 31 Mar 2009)
Log Message:
Merged (back ported) trunk revisions 4460,4492,4516,4520,4585,4630,4692,4726,4964 -> 3.x
http://10.171.12.252/svn/opensource/flex/sdk/trunk
r4460 | [email protected] | 2009-01-08 20:53:33 -0500 (Thu, 08 Jan 2009) | 10 lines
Renamed UIComponentAccImpl to UIComponentAccProps because it extends AccessibilityProperties, not AccessibilityImplementation.
Added comments with the identifier for each magic role constant, so that it is easier to understand what roles our components are using.
Moved two static methods from UIComponentAccProperties to AccImpl because they make more sense there.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: None (no functional changes)
r4492 | [email protected] | 2009-01-12 17:47:10 -0500 (Mon, 12 Jan 2009) | 8 lines
Simplified how an accessibility class gets hooked into its corresponding component class.
We now do the hooking in the static method enableAccessibility(), which is called by code that is autogenerated by the compiler. Previously this method did nothing and the hooking happened at static initialization time. This allows us to remove the static var accessibilityHooked and the static method hookAccessibility() in each accessibility class.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa and Alex
r4516 | [email protected] | 2009-01-13 18:23:14 -0500 (Tue, 13 Jan 2009) | 16 lines
Accessibility changes to Panel and TitleWindow, as requested by Freedom Scientific.
These components now report their accessibility role as "grouping" rather than "window". Their accessibility name is now simply their title. They no longer report any child items. Their accessibility location is the bounding rect of the entire Panel or TitleWindow.
The AccessibilityImplementation continues to be attached to the titleBar, not to the Panel/TitleWindow, because the Flash Player ignores Sprites with an AccessibilityImplementation that are inside other Sprites with an AccessibilityImplementation. (The Flash accessibility model is flat, not hierarchical, and "child IDs" are only used for things like list items, not for controls in titled container.)
So although in the display hierarchy the Panel is a parent of its content controls, in the MSAA model it appears as their preceding sibling. JAWS will look at the "grouping" role and understand that because the bounding rect of the grouping includes some of its following siblings, they are "inside". (I don't know what this means in terms of what JAWS will actually speak.)
Also, the AccImpl class now implements getChildIDArray() to return an empty array, so that by default all components have 0 child items (rather than reporting an error).
Finally, subclasses with child items now compute how many they have and then call a new AccImpl utility method, createChildIDArray(), to create an Array that looks like [ 1, 2, 3, 4, 5 ].
QE Notes: None
Doc Notes: None
Bugs: SDK-12390, SDK-16340
Reviewer: Deepa
r4520 | [email protected] | 2009-01-13 20:07:53 -0500 (Tue, 13 Jan 2009) | 10 lines
Accessibility changes to List, DataGrid, Menu, and Tree, as requested by Freedom Scientific, to behave more like their corresponding standard Windows controls.
List, DataGrid, and Menu no longer report an accessibility value, either for the control itself or for its child items.
Tree no longer reports a value value for itself. For tree items the value is the indentation level as a String: "0", "1", "2", etc. Previously the top-level items had value "1" instead of "0".
QE Notes: None
Doc Notes: None
Bugs: SDK-17755
Reviewer: Deepa
r4585 | [email protected] | 2009-01-19 18:53:01 -0500 (Mon, 19 Jan 2009) | 6 lines
AccImpl now implements accSelect(). Although the implementation doesn't do anything, its existence is enough to avoid having the Player report an IAccessible "member not found" error when calling accSelect() on a child item.
QE Notes: None
Doc Notes: None
Bugs: SDK-16654
Reviewer: Jason
r4630 | [email protected] | 2009-01-22 19:54:13 -0500 (Thu, 22 Jan 2009) | 6 lines
Removed code in AccordionHeaderAccImpl and TabBarAccImpl where the child IDs were being adjusted up or down by 100000 for some unknown reason. Deneb (on Flash Player) and Nataliya and Jon (on JAWS) don't think this should be done.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa
r4692 | [email protected] | 2009-01-27 17:13:03 -0500 (Tue, 27 Jan 2009) | 9 lines
Fixed missing or misplaced 'break' statements in the eventHandler() methods of the mx.accessibility classes. These have probably been causing some unintented MSAA events to be dispatched.
Also, each accessible component now dispatches OBJ_NAMECHANGE when its toolTip or errorString property changes, because the MSAA name includes the tooltip or error tip.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa
r4726 | [email protected] | 2009-01-28 21:47:59 -0500 (Wed, 28 Jan 2009) | 16 lines
Accessibility changes to the MSAA name of several components, as requested by Freedom Scientific. These changes make Flex controls behave more like standard Windows controls.
In Accordion and TabBar, the name is now just what is displayed, without " Tab" or " Tab, Active" appended.
In ComboBox, List, and Tree, the name of each item is now just what it displays, without, for example, "2 of 7" appended.
Removed an artificial limit of 100000 items in List and Menu.
A Slider with an MXML id no longer returns that id as its name; no other component does this and id's are certainly no intended to be spoken.
Removed the getName() method of ComboBase, which isn't used.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Jason
r4964 | [email protected] | 2009-02-16 12:41:50 -0500 (Mon, 16 Feb 2009) | 7 lines
Modify AccImpl.as to add @private to _protected final function $eventHandler(event:Event):void_ to work around an ASdoc bug. i will remove it when the bug gets fixed.
QE Notes: None
Doc Notes: None
Bugs: -
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-12390
http://bugs.adobe.com/jira/browse/SDK-16340
http://bugs.adobe.com/jira/browse/SDK-17755
http://bugs.adobe.com/jira/browse/SDK-16654
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccordionHeaderA ccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AlertAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ButtonAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/CheckBoxAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ColorPickerAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ComboBaseAccImpl .as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ComboBoxAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DataGridAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DateChooserAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DateFieldAccImpl .as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/LinkButtonAccImp l.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ListAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ListBaseAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/MenuAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/MenuBarAccImpl.a s
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/PanelAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/RadioButtonAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/SliderAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TabBarAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TitleWindowAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TreeAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/containers/Panel.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/core/UIComponent.as
Added Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/UIComponentAccPr ops.as
Removed Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/UIComponentAccIm pl.as
Property Changed:
flex/sdk/branches/3.x/

Have 2 airport extreme base stations connected in chain. Airport utility shows slave unit without power. However, power is on slave unit, but status lights do not show up at all. Small green lights at each back port blink. Anyone have any ideas?

Have 2 airport extreme base stations connected in chain. Airport utility shows slave unit without power. However, power is on slave unit, but status lights do not show up at all. Small green lights at each back port blink. Anyone have any ideas?

Unfortunately, you are describing the symptoms of an AirPort Extreme with a failing (or failed) internal power supply.
As a last resort, try a Factory Default Reset on the AirPort Extreme as follows:
Power off the AirPort by pulling the power cord
Wait a minute or two
Hold in the reset button first, and keep holding it in for an additional 8-10 seconds while you simultaneously plug the power back into the AirPort
Release the reset button and allow a full minute for the AirPort to restart
Now try to configure the AirPort again. If you continue to see the same symptoms as before, the AirPort will need to be replaced.

Whether the fix(in Bug 883973 - crash in JSFunction::getExistingScript) is indeed being back-ported to a Firefox 24.x ESR release?"

Please continue with the existing question Firefox crashes [/questions/990856#answer-547733]
whether the fix(in Bug 883973 - crash in JSFunction::getExistingScript) is indeed being back-ported to a Firefox 24.x ESR release?"

Please continue with the existing question ''Firefox crashes'' [/questions/990856#answer-547733]
'' whether the fix is indeed being back-ported to a Firefox 24.x ESR release? ''
I will close this as a duplicate.
To answer this you should of course try the latest Firefox 24.4 esr not the plain Firefox 24 from the Release channel.

[svn:osmf:] 13042: Fix for FM-287, reinstating the main sample ( that uses serial and parallel composition), and making another pass at getting all the changed trait methods mapped correctly back- and forth between JS and Flash .

Revision: 13042
Revision: 13042
Author:   [email protected]
Date:     2009-12-17 03:45:27 -0800 (Thu, 17 Dec 2009)
Log Message:
Fix for FM-287, reinstating the main sample (that uses serial and parallel composition), and making another pass at getting all the changed trait methods mapped correctly back- and forth between JS and Flash.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-287
Modified Paths:
    osmf/trunk/apps/samples/framework/HTMLGatewaySample/HTMLGatewaySample.as
    osmf/trunk/apps/samples/framework/HTMLGatewaySample/html-template/index.template.html
    osmf/trunk/framework/MediaFramework/org/osmf/external/HTMLElement.as
    osmf/trunk/framework/MediaFramework/org/osmf/gateways/HTMLGateway.as

Perre wrote:I'm used to being able to pick one or a couple of songs and then adding it a specified playlist. Is this impossible in sonata?
It's clearly not impossible, just different than you expect. Create your playlist as you want it to appear in the Current tab (meaning don't dump every single song from your library in there, just the ones you want) and then save the playlist.
Perre wrote:And if I try to play the m3u file created (the one with every song listed) through freevo I get a message that the directory is empty. What am I doing wrong??
Look at save_absolute_paths_in_playlists in your mpd.conf.

[svn:bz-trunk] 22848: Add back the fix for Watson 2780086.

Revision: 22848
Revision: 22848
Author:   [email protected]
Date:     2011-10-02 11:00:09 -0700 (Sun, 02 Oct 2011)
Log Message:
Add back the fix for Watson 2780086. This was originally added in changelist 21123 and then backed out in changelist 21160.
Checkintests: passed
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/security/LoginManager.java

The problem is that the one available in the repo does not support sfz files (it only supports gig).
I just compiled the one from AUR. I don't know how I missed that, even though I looked for it in the AUR. It's working perfectly now.
I am curious though why the one directly from the site was not compiling.
Thanks a million for the tip

[svn:bz-trunk] 19598: Add back fix for BLZ-578.

Revision: 19598
Revision: 19598
Author:   [email protected]
Date:     2011-01-05 08:50:58 -0800 (Wed, 05 Jan 2011)
Log Message:
Add back fix for BLZ-578. This fix was reverted because the LCDS Spring integration code had a dependency on thread local stuff that was removed by this fix. The LCDS Spring integration code was updated to not have the dependency any more so we should be able to add this fix back.
Checkintests: passed.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-578
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/FlexContext.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

[svn:fx-trunk] 11685: Ensure that when a recycled renderer gets put back into the mix for reuse, if the item it is rendering has the caret on it, it should draw in the careted state.

Revision: 11685
Author:   [email protected]
Date:     2009-11-11 23:05:34 -0800 (Wed, 11 Nov 2009)
Log Message:
Ensure that when a recycled renderer gets put back into the mix for reuse, if the item it is rendering has the caret on it, it should draw in the careted state.
QE notes: If there's anyway to simulate a mustella test for this situation, we should add it to the List testsuite.
Doc notes: No
Bugs: http://bugs.adobe.com/jira/browse/SDK-24012
Reviewer: Ryan
Tests run: List, checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24012
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ListBase.as

Hi Jurgen,
Thanks for the information.Yes it is a common scenario where we are struggling when multiple transports occours,More over the fear of sequencing makes it more complicated in these situations.
Definitely this is a helpful solution.
Regards,
Kannan

[svn:fx-3.x] 12023: Back-porting a fix for Mike M.

Similar Messages

Maybe you are looking for