[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...
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] 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.asI 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... -
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 -
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. asI 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 -
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.asRevision: 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: 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.asLots 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. -
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 -
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.asLots 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] 10002: Gradient matrix transform fix
Revision: 10002
Author: [email protected]
Date: 2009-09-03 13:17:09 -0700 (Thu, 03 Sep 2009)
Log Message:
Gradient matrix transform fix
http://bugs.adobe.com/jira/browse/SDK-22928 - Gradient matrix transform applying incorrect transforms
Previously, the logic transformed the gradient to fill the shape bounds and then combined the matrix transform. Now using the same values for the discreet transform properties versus the matrix properties should result in the same appearance.
These changes are applied to LinearGradient, RadialGradient, LinearGradientStroke and RadialGradientStroke.
QE notes: Matrix transform behavior has changed
Doc notes: Need info on matrix behavior
Bugs: SDK-22928
Reviewer: Glenn
Tests run: spark/primitives
Is noteworthy for integration: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-22928
http://bugs.adobe.com/jira/browse/SDK-22928
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/LinearGradient.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/LinearGradientStroke.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RadialGradient.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RadialGradientStroke.as -
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.mxmlWalter 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:fx-trunk] 9145: Fixed leak in AnimateTransitionShader effect.
Revision: 9145
Author: [email protected]
Date: 2009-08-06 11:54:04 -0700 (Thu, 06 Aug 2009)
Log Message:
Fixed leak in AnimateTransitionShader effect. We now dispose any BitmapData objects that we create on the fly as part of setting up and playing the effect.
QE notes: None
Doc notes: None
Bugs: SDK-20273
Reviewer: Corey
Tests run: checkintests, Mustella (spark/effects/[AnimateShaderTransition|Wipe|CrossFade])
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-20273
Modified Paths:
flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as
Maybe you are looking for
-
Canon SX260HS no longer recognized by iPhoto
After upgrading to Mavericks my Canon SX260HS is no longer recognized by iPhoto. When plugged in to a USB port the system report shows the camera, but iPhoto does not mount the camera. The camera briefly displays "communication error" on its display.
-
MacBook 2nd display (mini-DVI-DVI (D)- VGA)?
I am trying to hook up a second display to my MacBook. The problem is that I don't have a mini-DVI to VGA adapter, but I have a mini-DVI to DVI, and a DVI to VGA adapters. So I connected my Apple mini-DVI to DVI, to my DVI to VGA, and then to my 2nd
-
Why are my addons no longer showing on addon bar?
I use the Latest BBC News 1.31.1 addon which, until a short time ago, was always present on my addon bar. I have also just downloaded the Watch UK TV 1.46.1 addon, but this does not appear on the addonbar either. Both addons are enabled (and both hav
-
Can I view slideshows via an USB cable on my television
I would like to watch my slideshows on my television, can I do this via a USN cable between the Apple Mac Pro and the televison's USB port
-
HT203172 ARDAgent permissions problem in regard to app
can u please tell me why a recently purchased app has crashed (bento4) and since then i have this permissions problem regarding ARDAgent??? most importantly the app only works when running on a different user!!!