[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

Similar Messages

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

  • [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] 4885: Flex SDK Framework - Update mx.filters API and class hierarchy

    Revision: 4885
    Author: [email protected]
    Date: 2009-02-06 16:12:32 -0800 (Fri, 06 Feb 2009)
    Log Message:
    Flex SDK Framework - Update mx.filters API and class hierarchy
    - Removed BaseFilter.as, BaseDimensionFilter.as, and GradientFilter.as
    - Renamed IBitmapFilter.as to IFlexBitmapFilter.as
    - Changed IBitmapFilter.clone to createBitmapFilter
    - Moved properties and functions from base classes up to filter subclasses
    - Changed ColorMatrixFilter constructor parameter from Array to Object
    - Added Change metadata to all filter classes
    - Changed notifyFilterChanged from public to private
    - Added ASDoc comments
    - Added copyright info
    - Added a number of formatting and style fixes
    QE Notes: Need to update tests based on API changes. Missing tests for DisplacementMapFilter.as.
    Doc Notes: Need extensive ASDoc review. Consider using @copy for properties that match the flash.filters properties
    Bugs: n/a
    Reviewer: Gordon
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateFilterInst ance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/BevelFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/BlurFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/ColorMatrixFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/ConvolutionFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/DisplacementMapFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/DropShadowFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/GlowFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/GradientBevelFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/GradientGlowFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/ShaderFilter.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Parser.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/StrokedElement.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s
    flex/sdk/trunk/frameworks/projects/framework/src/FrameworkClasses.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    Added Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/filters/IFlexBitmapFilter.as
    Removed Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/filters/GradientFilter.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/filters/BaseDimensionFilter.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/filters/BaseFilter.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/filters/IBitmapFilter.as

    Yup. The source files are simply missing from the 4.5 source releases....I'm hitting the same issue when trying to rebuild the SDK with flexcover changes applied.

  • [svn:osmf:] 11205: Fix bug FM-169: Trait support for data transfer sample doesn' t display bytes loaded and bytes total for SWF element

    Revision: 11205
    Author:   [email protected]
    Date:     2009-10-27 15:04:26 -0700 (Tue, 27 Oct 2009)
    Log Message:
    Fix bug FM-169: Trait support for data transfer sample doesn't display bytes loaded and bytes total for SWF element
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-169
    Modified Paths:
        osmf/trunk/apps/samples/framework/PluginSample/src/PluginSample.mxml
        osmf/trunk/apps/samples/framework/PluginSample/src/org/osmf/model/Model.as

    The bug is known, and a patch has been submitted: https://bugs.freedesktop.org/show_bug.cgi?id=80151. There's been no update since friday, so I wonder what the current status is, or if it's up for review at all.
    Does anyone know how we can be notified when this patch hits the kernel?

  • [svn:osmf:] 10440: Add parser support for the Video tag.

    Revision: 10440
    Author:   [email protected]
    Date:     2009-09-20 15:03:56 -0700 (Sun, 20 Sep 2009)
    Log Message:
    Add parser support for the Video tag.  Add unit test for an empty document.
    Modified Paths:
        osmf/trunk/libs/VAST/.flexLibProperties
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTInlineAd.as
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/parser/VASTParser.as
        osmf/trunk/libs/VASTTest/org/openvideoplayer/vast/parser/TestVASTParser.as
    Added Paths:
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTMediaFile.as
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTVideo.as

    The video tag only supports a few formats and MKV (Matroska Multimedia Container) isn't one of them.<br />
    Your only option is to use the object (or embed) tag and use a player that can handle that format.<br />
    If might be better to switch to the WebM format.<br />
    * https://developer.mozilla.org/En/Media_formats_supported_by_the_audio_and_video_elements

  • [svn] 3624: Enabling initial support for colorTransform in GraphicElement.

    Revision: 3624
    Author: [email protected]
    Date: 2008-10-14 08:35:30 -0700 (Tue, 14 Oct 2008)
    Log Message:
    Enabling initial support for colorTransform in GraphicElement.
    Bugs: MXMLG-241
    Check-in Tests: Pass
    Reviewer: Chet, Ryan, Jason
    QA: Yes
    Ticket Links:
    http://bugs.adobe.com/jira/browse/MXMLG-241
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

    I guess GraphicElement will never support automation, at least by the time of Flex 4 release.
    During my tests with GraphicElement extending IAutomationObject interface, I've just hit RTE coming from closed-source mx.automation.AutomationManager class requesting the automated UI control to implement IUIComponent interface, and obviuosly GraphicElement class does not implement this interface
    TypeError: Error #1034: Type Coercion failed: cannot convert GraphicElementAutomation@7b10e19 to mx.core.IUIComponent.
         at mx.automation::AutomationManager/getChildren()[C:\work\flex\dmv_automation\projects\automation\src\mx\automation\AutomationManager.as:1157]

  • Fixed quantity not supported for alternative items

    Hi dears,
    I was trying to configure in a Bill of Material a group of components marked together as "Alternative item", having the Fixed quantity indicator set (so the quantity is not in proportioned with the order quantity).
    However, when I do this action I have the error message no. 29485 "Fixed quantity not supported for alternative items", because a fixed quantity is not allowed for alternative items.
    Leaving out the fact that I don't understand for which kind of logic this should be done, do you know if there is any solution to achive the same result (use alternative item and each of them should be with fixed quantity despite th eorder quantity)?
    Thanks and regards,
    Giovanni

    Daily structure relationship step: remove relation
    CLOSING

  • [Consolidation-Locked] Please add RAW support for the Nikon D600 to Lightroom as soon as possible!

    My Fair Adobe,
    Please add RAW support for the Nikon D600 to Lightroom as soon as possible!
    ViewNX lets me get to the images, but come on!!! I know Lightroom, and you, ViewNX, are no Lightroom.
    Yes, I see everyone else ASKING for D600 support. I'm here to beg for it! Don't make me wait much longer!
    Message title was edited by: Brett N
    Message title was edited by: Brett N

    Rob, my reading of your site is that this plug-in copies settings from raw to jpeg, does it work the other way around as well?
    Rob Cole wrote:
    One of the great things about the new 0-based defaults and linear tone curve is:
    You can develop the jpegs now, in Lightroom, and then sync the settings to the raws later (e.g. using RawPlusJpeg), and provided you select a matching camera profile, they will look almost the same (white balance won't translate over, but everything else will, more or less). Beware lens corrections applied to the raws might alter the registration of precision local adjustments.
    Note: I recommend shooting with ADL off in order for this to work better, and consider turning sharpening off in camera as well, and noise reduction and everything else to whatever extent is possible.
    Rob

  • Are you planning to add SFTP support for Muse CC at some point?

    Are you planning to add SFTP support for Muse CC at some point? Would that be in the near future? (I have successfully used the FTP module many times, my question refers to SFTP or FTPS protocols, not currently supported, an honestly, pretty necessary). Right now we have to use an external FTP client, which is a hassle.

    We don't pre-announce our future plans.
    If you'd like more visibility into future plans and access to Beta builds, all active subscribers who can accept the terms of the Non-Disclosure Agreement are invited to join the Adobe Muse Private Beta Program by visiting http://museprerelease.com

  • [svn:fx-trunk] 11717: Bug Fixing Localized SDK - modified one file xercesSchema. properties in xercesImpl_ja.jar - added " to one JA string.

    Revision: 11717
    Author:   [email protected]
    Date:     2009-11-12 11:54:22 -0800 (Thu, 12 Nov 2009)
    Log Message:
    Bug Fixing Localized SDK - modified one file xercesSchema.properties in xercesImpl_ja.jar - added " to one JA string.
    ANT CLEAN MAIN successful
    Modified Paths:
        flex/sdk/trunk/lib/xercesImpl_ja.jar

  • [svn:bz-trunk] 18840: bug fix of BLZ-576, add the initialization to one of the counter

    Revision: 18840
    Revision: 18840
    Author:   [email protected]
    Date:     2010-11-29 12:41:55 -0800 (Mon, 29 Nov 2010)
    Log Message:
    bug fix of BLZ-576, add the initialization to one of the counter
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-576
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/management/runtime/messaging/endpoints/EndpointContro l.java

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • [svn:bz-trunk] 18839: bug fix BLZ-575 Potential race condition in flex. management.runtime.messaging.endpoints.EndpointControl

    Revision: 18839
    Revision: 18839
    Author:   [email protected]
    Date:     2010-11-29 12:26:32 -0800 (Mon, 29 Nov 2010)
    Log Message:
    bug fix BLZ-575 Potential race condition in flex.management.runtime.messaging.endpoints.EndpointControl
    Change a few counters to Atomic numbers
    Probably solve some PMD bugs too (was complaining about new Integer() and new Long() API)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-575
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/management/runtime/messaging/endpoints/EndpointContro l.java

Maybe you are looking for