[svn:fx-trunk] 10135: Fix to effects' transform center functionality.

Revision: 10135
Author:   [email protected]
Date:     2009-09-10 15:38:22 -0700 (Thu, 10 Sep 2009)
Log Message:
Fix to effects' transform center functionality. When autoCenterTransform=false, should default to the transformX/Y/Z specified in the target object. We were instead defaulting to a default Vector3D(), which is like having transfomrXYZ at (0,0,0). one-liner fix to initialize the default transform center with the target's transformXYZ values.
Also fixed unrelated typo in UIComponent asdocs.
QE notes: None
Doc notes: None
Bugs: sdk-21766
Reviewer: Jason
Tests run: checkintests, Mustella transform effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-21766
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

I had downloaded it for test, and requested for evaluation license...
But I haven't got license, and also I am not able to find Flash Builder Plugins from HFCD site....
I think those plugins are removed from site....
Please help me, if anyone have those plugins...

Similar Messages

  • [svn:fx-trunk] 10229: Fixes for some transform effects problems.

    Revision: 10229
    Author:   [email protected]
    Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
    Log Message:
    Fixes for some transform effects problems.
    - We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
    - A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
    - A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
    QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
    Doc notes: None
    Bugs: sdk-23177
    Reviewer: Hans
    Tests run: checkintests, Mustella transform effects
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-23177
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

  • [svn:fx-trunk] 8491: * Fixed NPE caused by SkinPart functionality when metadata has a typo.

    Revision: 8491
    Author:   [email protected]
    Date:     2009-07-09 13:03:59 -0700 (Thu, 09 Jul 2009)
    Log Message:
    Fixed NPE caused by SkinPart functionality when metadata has a typo.
    tests Passed: checkintests
    Needs QA: YES
    Needs DOC: NO
    Bug fixes: SDK-22073
    API Change: NO
    Is noteworthy for integration: No
    Code-level description of changes:
      Modified evaluate(Context cx, MetaDataNode node) to check for a null
      id before comparing it.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22073
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/TypeAnalyzer.java

  • [svn:fx-trunk] 11894: Fix ASC-3586 ( NPE analyzing function definition in dead code)

    Revision: 11894
    Revision: 11894
    Author:   [email protected]
    Date:     2009-11-17 07:58:11 -0800 (Tue, 17 Nov 2009)
    Log Message:
    Fix ASC-3586 (NPE analyzing function definition in dead code)
    Original patch author: Jeff Dyer
    Reviewer: Tom Harwood
    Tests: asc/tamarin/flex acceptance tests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/ASC-3586
    Modified Paths:
        flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/ConstantEvaluator.java

  • [svn] 4611: Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.

    Revision: 4611
    Author: [email protected]
    Date: 2009-01-21 16:30:21 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.
    QE Notes: None
    Doc Notes: None
    Bugs: sdk-17783, sdk-18767, sdk-18759, sdk-18461, sdk-18309, sdk-18013, sdk-18688
    Reviewer: Jason
    Tests: checkintests, Mustella: Effects, gumbo/effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-17783
    http://bugs.adobe.com/jira/browse/sdk-18767
    http://bugs.adobe.com/jira/browse/sdk-18759
    http://bugs.adobe.com/jira/browse/sdk-18461
    http://bugs.adobe.com/jira/browse/sdk-18309
    http://bugs.adobe.com/jira/browse/sdk-18013
    http://bugs.adobe.com/jira/browse/sdk-18688
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateShaderTransition.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/SetAction.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateShaderTran sitionInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/EffectInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Parallel.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetPropertyAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetStyleAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/UnconstrainItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/ParallelInstanc e.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

    Revision: 4611
    Author: [email protected]
    Date: 2009-01-21 16:30:21 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.
    QE Notes: None
    Doc Notes: None
    Bugs: sdk-17783, sdk-18767, sdk-18759, sdk-18461, sdk-18309, sdk-18013, sdk-18688
    Reviewer: Jason
    Tests: checkintests, Mustella: Effects, gumbo/effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-17783
    http://bugs.adobe.com/jira/browse/sdk-18767
    http://bugs.adobe.com/jira/browse/sdk-18759
    http://bugs.adobe.com/jira/browse/sdk-18461
    http://bugs.adobe.com/jira/browse/sdk-18309
    http://bugs.adobe.com/jira/browse/sdk-18013
    http://bugs.adobe.com/jira/browse/sdk-18688
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateShaderTransition.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/SetAction.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateShaderTran sitionInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/EffectInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Parallel.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetPropertyAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetStyleAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/UnconstrainItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/ParallelInstanc e.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

  • [svn:fx-trunk] 12293: Fix ASC-3726: implement ECMA-262 style numeric conversions for constant numerics.

    Revision: 12293
    Revision: 12293
    Author:   [email protected]
    Date:     2009-11-30 13:23:52 -0800 (Mon, 30 Nov 2009)
    Log Message:
    Fix ASC-3726: implement ECMA-262 style numeric conversions for constant numerics.
    Tests: asc,flex,tamarin checkin tests
    Review: Jeff Dyer (src), Chris Peyer (tests)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/ASC-3726
        http://bugs.adobe.com/jira/browse/ECMA-262
    Modified Paths:
        flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/ConstantEvaluator.java
    Added Paths:
        flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/NumericConversions.java
    Removed Paths:
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPrivInstMethArg ValIntErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPrivInstMethArg ValUintErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPubInstMethArgV alIntErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPubInstMethArgV alUintErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefInstMethArgValErr .err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefInstMethArgValuin tErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefMethArgValErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefMethArgValuintErr .err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefPackMethArgValErr .err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefPackMethArgValUin tErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefStatMethArgValErr .err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefStaticMethArgValU intErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvIntClDefInstMethArgU intErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPrivInstMethArg ValIntErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPrivInstMethArg ValUintErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPubInstMethArgV alUintErr.err
        flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPubInstMethArgV alintErr.err

  • [svn:fx-trunk] 13133: Fix to transform effects to ignore projection on 2D effects.

    Revision: 13133
    Revision: 13133
    Author:   [email protected]
    Date:     2009-12-21 16:02:54 -0800 (Mon, 21 Dec 2009)
    Log Message:
    Fix to transform effects to ignore projection on 2D effects. The prior implementation meant that even 2D effects, like Move, would cause us to set the projection information on a target object's container, even though we were not changing 3D values.
    The fix is to set the default values of the projection properties to false in AnimateTransformInstance. That way, any 3D effect (AnimateTransform3D or its subclasses) would cuase the properties to be set according to the 3D defaults (or values that the developer set them to), whereas any 2D effect would leave the values false, which would result in our ignoring the projection matrix for that effect.
    QE notes: Breaks several AnimateTransform tests in Mustella, but new behavior is correct and tests should be updated (they have been excluded for now)
    Doc notes: None
    Bugs: SDK-24396
    Reviewer: Ely
    Tests run: Checkintests, Mustella sparrk transform effects (AnimateTransform, Move, AnimateTransform3D, etc.)
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24396
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    I had downloaded it for test, and requested for evaluation license...
    But I haven't got license, and also I am not able to find Flash Builder Plugins from HFCD site....
    I think those plugins are removed from site....
    Please help me, if anyone have those plugins...

  • [svn:fx-trunk] 6642: Fix for bug when doing a Resize and a transform effect in a Parallel transition with autoCenterTransform =true.

    Revision: 6642
    Author:   [email protected]
    Date:     2009-05-05 08:18:04 -0700 (Tue, 05 May 2009)
    Log Message:

    Revision: 6642
    Author:   [email protected]
    Date:     2009-05-05 08:18:04 -0700 (Tue, 05 May 2009)
    Log Message:

  • [svn:fx-trunk] 10131: Fixes to several effects bugs and one styles-related bug.

    Revision: 10131
    Author:   [email protected]
    Date:     2009-09-10 14:25:42 -0700 (Thu, 10 Sep 2009)
    Log Message:
    Fixes to several effects bugs and one styles-related bug.
    QE notes: Fixes to all filed auto-center feature bugs.
    Doc notes: None
    Bugs: sdk-22994, sdk-22992, sdk-22990, sdk-21850, sdk-22973
    Reviewer: Jason (+Glenn for RadioButton/CheckBox changes, 21850)
    Tests run: checkintests, Mustella (transform effects, Slider, DataGrid - all passed last week, prior to skin/test changes)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-22994
        http://bugs.adobe.com/jira/browse/sdk-22992
        http://bugs.adobe.com/jira/browse/sdk-22990
        http://bugs.adobe.com/jira/browse/sdk-21850
        http://bugs.adobe.com/jira/browse/sdk-22973
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/CheckBox.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/RadioButton.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SoundEffectInst ance.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
        flex/sdk/trunk/tools/dependencychecker/frameworkSwcExceptionsList.txt

  • [svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

    Revision: 10898
    Author:   [email protected]
    Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
    Log Message:
    Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
    The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler).  Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch.  So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility.  Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
    QE notes: -
    Doc notes: -
    Bugs: SDK-23263
    Reviewer: Darrell
    Tests run: checkintests, Rob ran mustella window/windowedapplication
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23263
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

    I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +41.0°C  (high =   +80°C, hyst =   +75°C)   sensor = PII/Celeron diode 
    Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
    Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +16.0°C  (high =   +80°C, hyst =   +75°C)   sensor = 3904 transistor 
    Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
    So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.  
    I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C.   Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

  • [svn:fx-trunk] 10960: Fixed performance of Wipe effect.

    Revision: 10960
    Author:   [email protected]
    Date:     2009-10-09 13:55:47 -0700 (Fri, 09 Oct 2009)
    Log Message:
    Fixed performance of Wipe effect. It turns out that micro-tuning the shader code is very important, since that same inner loop runs on every pixel of the bitmap being affected. This change splits the single Wipe shader (with a direction parameter) into four separate Wipe shaders (WipeLeft, etc.), to avoid a switch on the direction parameter. Also, it avoids some setup of pixel values, only bothering to sample the pixel values after it determines which image to sample from. Little stuff, but gained about 20-25% performance on some sample wipe effects.
    QE notes: This broke 3 Wipe effects tests because the old WipeEffectInstance class went away. These tests have supposedly been updated by the time this checkin is happening.
    Doc notes: No
    Bugs: sdk-23279
    Reviewer: Corey
    Tests run: checkintests, mustella spark/effects
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-23279
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.as
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbk
    Removed Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/WipeInstance.as

  • [svn:fx-trunk] 5473: Fix for bug around handling of constraints during and after effects were run , both for old and new effects.

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.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] 8551: Fix for focusSkin and errorSkin to account for bogus bitmap snapshots when objects are 3D transformed .

    Revision: 8551
    Author:   [email protected]
    Date:     2009-07-14 11:31:50 -0700 (Tue, 14 Jul 2009)
    Log Message:
    Fix for focusSkin and errorSkin to account for bogus bitmap snapshots when objects are 3D transformed.
    Bugs: SDK-17766
    Reviewer: Glenn
    QE Notes: None
    Doc Notes: None
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-17766
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/ErrorSkin.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/FocusSkin.as

  • [svn:fx-trunk] 12978: Fix for possible null deref in Effect. captureMoreStartValues().

    Revision: 12978
    Revision: 12978
    Author:   [email protected]
    Date:     2009-12-15 17:12:29 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Fix for possible null deref in Effect.captureMoreStartValues(). Seems unlikely to ever occur since the function is not really there for random calling outside of data effects, but the fix was simple.
    QE notes: none
    Doc notes: none
    Bugs: sdk-16451
    Reviewer: Jason
    Tests run: checkintests, Mustella mx/effects, mx/ListDataEffects
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-16451
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

Maybe you are looking for

  • I have just purchased ARD 3.3, how many computers can I install it on?

    I purchase the unlimtied option (but I know that is how many clients I can manage.) I want to be able to manage the machines on two different computers. Will I need two copies? Thanks

  • How to Read/Write to PS registry, tools for making GUI

    Hi Folks, We have several plugins that we would like to make available to our users by the Photoshop panel (made with Adobe Configurator). Plugins are scripting aware, and also use reading and writing to Photoshop registry. We also want that user can

  • Problem with new-line-character and java.io.LineNumberReader under AIX

    Hi folks, I got the following problem: I wrote a little parser that reads in a plain-text, tabulator-separated, line-formatted logfile (and later on safes the data to a 2-dimensional Vector). This logfile was originally generated by an AIX ksh script

  • Changes in plant specific info record...Urgent!!!

    Hi All, I changed the order unit in one of the plant specific info record and it resulted in a change in the generic info record (without any plant) for the same material & vendor. Can anyone let me know why its happening as I am making the changes t

  • InDesign CS4 crash

    hi All I hope you can help! I have an InDesign CS4 file that has been working fine but today crashed and will not open now. I get the "file may be damaged" warning and when I hit OK to open anyway, then InDesign crashes (just the program, not my whol