[svn:fx-trunk] 9284: Fix bug: Spark BasicLayout should throw error/ RTE when setting useVirtualLayout

Revision: 9284
Author:   [email protected]
Date:     2009-08-13 15:33:07 -0700 (Thu, 13 Aug 2009)
Log Message:
Fix bug: Spark BasicLayout should throw error/RTE when setting useVirtualLayout
QE notes: None
Doc notes: None
Bugs: SDK-22211
Reviewer: Hans
Tests run: checkintests, gumbo/core/Group, gumbo/core/DataGroup, gumbo/core/List
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22211
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/bundles/en_US/layout.properties
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/BasicLayout.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.

Similar Messages

  • [svn:fx-trunk] 9225: Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization

    Revision: 9225
    Author:   [email protected]
    Date:     2009-08-11 11:36:09 -0700 (Tue, 11 Aug 2009)
    Log Message:
    Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization
    Fix: Change H/V layouts first-visible-element lookup logic to accommodate negative gaps.
    QE notes: None
    Doc notes: None
    Bugs: SDK-22497
    Reviewer: Hans
    Tests run: checkintests,
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22497
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as

    sorka;
    You can check the LabVIEW Support page.
    There is a troubleshooting section called LabVIEW Installation/Getting Started Resources. It also includes a LabVIEW 7.x Frequently Asked Questions that has a link that reads Issues Fixed in LabVIEW 7.1. However, not much information is provided there.
    Other places where you can post your findings is at the LAVA Forum (check the Bug list forum) and the Info-LabVIEW mailing list. These are not official places, but usually they li
    sten
    Enrique
    www.vartortech.com

  • [svn:fx-trunk] 5831: Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit

    Revision: 5831
    Author: [email protected]
    Date: 2009-03-31 16:50:47 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit
    Fix: implement text reflow support for TextGraphicelement.
    QE Notes: None
    Doc Notes:
    Bugs: SDK-19800
    Reviewer: Carol, Gordon
    tests: checkintests, mustella
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19800
    http://bugs.adobe.com/jira/browse/SDK-19800
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/supportClasses/TextGraphicE lement.as

  • [svn:fx-trunk] 9287: Fixes bug with shader-transition effects ( AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters .

    Revision: 9287
    Author:   [email protected]
    Date:     2009-08-13 15:53:43 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fixes bug with shader-transition effects (AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters. Fix was to capture the bitmap snapshot of the target without any of its own filters applied and to then use the ShaderFilter in conjunction with the target's filters during the animation.
    QE notes: Probably need more tests in this area, now that we handle it
    Doc notes: none
    Bugs: sdk-20250
    Reviewer: Jason
    Tests run: Checkintests, Mustella (spark/effects/[AnimateTransitionShader|Wipe|CrossFade])
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-20250
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransitionShader.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

  • [svn:fx-trunk] 9324: Fix bug: orientation/verticalAlign/ horizontalAlign properties of TileLayout should not be bindable

    Revision: 9324
    Author:   [email protected]
    Date:     2009-08-14 15:04:23 -0700 (Fri, 14 Aug 2009)
    Log Message:
    Fix bug: orientation/verticalAlign/horizontalAlign properties of TileLayout should not be bindable
    Fix: remove metadata, we were not dispatching events anyway.
    QE notes: None
    Doc notes: None
    Bugs: SDK-22715
    Reviewer: Hans
    Tests run: build
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22715
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/TileLayout.as

    to put it simple, the DataGrid supposely changes the dataProvider on each page (page here is actually the selection in the list. since the list displays only one item at one time, I just called each selection as page) . So, I was thinking to refresh the itemRenderer on each swipe. could be there are any other way to do this so appreciate any help and ideas. Thanks!

  • [svn:fx-trunk] 9275: Fix bug: GraphicElement.getStrokeExtents needs ASDoc

    Revision: 9275
    Author:   [email protected]
    Date:     2009-08-13 12:05:09 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fix bug: GraphicElement.getStrokeExtents needs ASDoc
    Fix: Add comment, while at it, updated the API to return a Rectangle instead.
    QE notes: None
    Doc notes: None
    Bugs: FLEXDOCS-1032
    Reviewer: Deepa
    Tests run: checkintests, spark/primitives, gumbo/layout/graphicElements
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1032
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Ellipse.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Rect.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/StrokedEleme nt.as

  • [svn:fx-trunk] 7891: Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets .

    Revision: 7891
    Author:   [email protected]
    Date:     2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
    Log Message:
    Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets.
    QE Notes: none
    Doc Notes: None
    Bugs: SDK-21839
    Reviewer: Evtim
    Tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21839
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

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

  • [svn:fx-trunk] 12786: Fixed bug with state property value assignments.

    Revision: 12786
    Revision: 12786
    Author:   [email protected]
    Date:     2009-12-10 07:35:43 -0800 (Thu, 10 Dec 2009)
    Log Message:
    Fixed bug with state property value assignments. SetProperty pseudonym values (width/explicitWidth, height/explicitHeight) were not getting set correctly, causing values to be incorrectly assigned to 0 in some cases.
    QE notes: -
    Doc notes: -
    Bugs: sdk-24446
    Reviewer: Corey
    Tests run: checkintests, Mustella tests/States, tests/mx/states
    Is noteworthy for integration: Yes (fix requested by tools)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24446
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/states/SetProperty.as

    Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
    margin-bottom: -2px;
    Your nav p will then look like this:
    nav p {
              font-size: 90%;
              font-weight: bold;
              color: #FFC;
              background-color: #090;
              text-align: right;
              padding-top: 5px;
              padding-right: 20px;
              padding-bottom: 5px;
              border-bottom-width: 2px;
              border-bottom-style: solid;
              border-bottom-color: #060;
              background-image: url(images/background.png);
              background-repeat: repeat-x;
              margin-bottom: -2px;

  • [svn:fx-trunk] 9890: Fix bug involving changes to tabbing related properties

    Revision: 9890
    Author:   [email protected]
    Date:     2009-09-01 15:57:01 -0700 (Tue, 01 Sep 2009)
    Log Message:
    Fix bug involving changes to tabbing related properties
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-19577
    Reviewer: Corey
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests mustella/managers/FocusManager
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-19577
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/FocusManager.as

  • [svn:fx-trunk] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

    Revision: 7868
    Author:   [email protected]
    Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
    Log Message:
    Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
    Modified Paths:
        flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

    Walter Laan wrote:
    almightywiz wrote:
    Walter Laan wrote:
    The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
    The only browser so far that works as I'd expect, or at least as I'd like, is IE.
    Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
    Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
    Removed table which has now been expanded & added to 1st post.

  • [svn] 4793: Fix bug SDK-17734 Path with width and height set different than path data has incorrect bounds

    Revision: 4793
    Author: [email protected]
    Date: 2009-02-02 11:20:06 -0800 (Mon, 02 Feb 2009)
    Log Message:
    Fix bug SDK-17734 Path with width and height set different than path data has incorrect bounds
    Fix: When calculating the bounds position we should take into account the implicit scaling factor actualSize/naturalSize. Also did some refactoring, getting rid of the protected method calculateTopLeft.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17734
    Reviewer: Ryan
    tests: mustella gumbo/layout/GraphicElement
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17734
    http://bugs.adobe.com/jira/browse/SDK-17734
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Ellipse.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Path.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

    Thank you so much for replying.
    Yes I have removed and reinstalled WMP.
    I had good results with the PD6 application installed on the default path onto the C: drive with the one exception that if the application was launched by accident and the user data path was not available, the PD6 application would blow away my custom user path registry settings. Now that I know what they are I have made a .reg file to repair my registry to my desired user data paths.
    Installing the application on the removable drive appeared to help prevent me from launching the application by accident and overwriting my registry with default user paths.
    So which is the less of the two evils?
    If the application directory is not available, windows media player still tries to launch the .msi for installing PD6.
    If I install the application to the C: drive but the user data to the removable drive, launching the PD6 application without the user data drive will still corrupt my registry settings for a user data path.
    Both these issues seem like a logical (if not easy) fix that should be done in the PD6 application and installation package. I mean really, cannot anyone tell me why windows media player is checking the PD6 application directory? Why in PD4 did we have an option control for setting the user data path from the PD4 application? Why is this option not in the PD6 application, just the installer?
    I am given a choice during installation to move the user data to another non default location. Why else would this be provided if not to accommodate my kind of request to store the user data into an alternate location other than “My Document”. Certainly Palm is not trying to force the users on how to protect and store their personal data?
    Post relates to: Centro (Verizon)

  • [svn] 4619: Bug: BLZ-313 - HTTPProxyService throws null pointer when non-turnkey BlazeDS app is deployed to Tomcat 6 .0.16

    Revision: 4619
    Author: [email protected]
    Date: 2009-01-22 10:47:12 -0800 (Thu, 22 Jan 2009)
    Log Message:
    Bug: BLZ-313 - HTTPProxyService throws null pointer when non-turnkey BlazeDS app is deployed to Tomcat 6.0.16
    QA: Yes
    Doc: No
    Checkintests: Pass
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-313
    Modified Paths:
    blazeds/trunk/modules/proxy/src/flex/messaging/services/HTTPProxyService.java

    I submitted a bug, and this was fixed in the latest trunk
    version.

  • [svn] 1338: Bug: BLZ-123-Attempting to use a channel that doesn' t support messaging (AMFChannel/AMFEndpoint withtout polling enabled) should throw error

    Revision: 1338
    Author: [email protected]
    Date: 2008-04-22 07:45:18 -0700 (Tue, 22 Apr 2008)
    Log Message:
    Bug: BLZ-123-Attempting to use a channel that doesn't support messaging (AMFChannel/AMFEndpoint withtout polling enabled) should throw error
    QA: Yes
    Doc: No
    Details: Added logic in Consumer such that when the Consumer is connected over a non-realtime channel (i.e. non-polling and non-streaming channel), a warning is logged to let the user know that channel is not going to automatically receive updates via client poll or server push. We can't really throw an error here because one might want to disable channel polling and manually send poll requests when needed and this is a valid configuration as well.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-123
    Modified Paths:
    flex/sdk/branches/3.0.x/frameworks/projects/rpc/src/mx/messaging/AbstractConsumer.as

    Thanx Mete, yeah i did...
    but i solved it some other way... not entirely sure this was
    it though as i was doing a lot of things at once...
    it was fds.swc... possibly it was out of date or missing.

  • [svn:fx-trunk] 16331: Form Bug Fixes

    Revision: 16331
    Revision: 16331
    Author:   [email protected]
    Date:     2010-05-26 17:20:51 -0700 (Wed, 26 May 2010)
    Log Message:
    Form Bug Fixes
    SDK-26517 - Form should take into account includeInLayout property when calculating baselineElementPosition
    Added logic into Group to find the first element that has includeInLayout == true.
    SDK-26509 - Spark Form shows dual error strings in non-stacked layout
    Removed error string from FormSkin. Created a StackedFormSKin skin which includes the error string.
    SDK-26499 - Spark Form skin should use errorStringDisplay skin part instead of errorStringText
    Changed name to errorTextDisplay
    SDK-26498 - Spark Form needs more padding around error strings
    Added padding to the entire Form
    SDK-26503 - Difficult to create custom Spark FormItem skin due to embedded required/error icon assets
    Added new requiredIndicatorSource and errorIndicatorSource styles to FormItem. FormItem skins now grab the icons from these styles. Custom skin also have access to these icons.
    QE notes: Form layout has changed
    Doc notes: none
    Bugs: SDK-26517, SDK-26509, SDK-26499, SDK-26498, SDK-26503
    Reviewer: Kevin
    Tests run: checkintests
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-26517
        http://bugs.adobe.com/jira/browse/SDK-26509
        http://bugs.adobe.com/jira/browse/SDK-26499
        http://bugs.adobe.com/jira/browse/SDK-26498
        http://bugs.adobe.com/jira/browse/SDK-26503
        http://bugs.adobe.com/jira/browse/SDK-26517
        http://bugs.adobe.com/jira/browse/SDK-26509
        http://bugs.adobe.com/jira/browse/SDK-26499
        http://bugs.adobe.com/jira/browse/SDK-26498
        http://bugs.adobe.com/jira/browse/SDK-26503
    Modified Paths:
        flex/sdk/trunk/frameworks/build_framework.xml
        flex/sdk/trunk/frameworks/projects/spark/build.xml
        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/FormItem.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/FormHeadingSkin.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/FormItemSkin.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/FormSkin.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/StackedFormHeadingSkin.mxm l
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/StackedFormItemSkin.mxml
        flex/sdk/trunk/frameworks/tests/basicTests/spark/scripts/FormTestScript.mxml
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/assets/
        flex/sdk/trunk/frameworks/projects/spark/assets/ErrorIndicator.png
        flex/sdk/trunk/frameworks/projects/spark/assets/RequiredIndicator.png
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/StackedFormSkin.mxml
    Removed Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/assets/ErrorIndicator.png
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/assets/RequiredIndicator.p ng

    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.

Maybe you are looking for