[svn:fx-trunk] 8602: Fix RTE after setting baseColor.

Revision: 8602
Author:   [email protected]
Date:     2009-07-15 15:06:23 -0700 (Wed, 15 Jul 2009)
Log Message:
Fix RTE after setting baseColor.
https://bugs.adobe.com/jira/browse/SDK-21749
TitleBarSkin:
Remove items form color exclusion array. Remove ?\226?\128?\156bgFill?\226?\128?\157 because it is not of type DisplayObject or GraphicElement. Remove ?\226?\128?\156background?\226?\128?\157 because it is part of the window chrome and should be affected by baseColor.
SparkSkin:
Only process excluded objects of type DisplayObject or GraphicElement in updateDisplayList().
https://bugs.adobe.com/jira/browse/SDK-21625
Spark and Halo WindowedApplication/Window:
Update class comments and remove dead code.
QE Notes: none.
Doc Notes: none.
Bugs: SDK-21749, SDK-21625.
Reviewer: Glenn
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21749
    http://bugs.adobe.com/jira/browse/SDK-21625
    http://bugs.adobe.com/jira/browse/SDK-21749
    http://bugs.adobe.com/jira/browse/SDK-21625
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
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/skins/spark/windowChrome/TitleB arSkin.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/SparkSkin.as

Similar Messages

[svn:fx-trunk] 8883: Fixes RTE seeking into Sequences.

Revision: 8883
Author:   [email protected]
Date:     2009-07-28 16:05:56 -0700 (Tue, 28 Jul 2009)
Log Message:
Fixes RTE seeking into Sequences. Seeking (setting playheadTime) to or past the end of the Sequence would not properly end the effect and would set it up for failure on future playing.
QE notes: None
Doc notes: None
Bugs: sdk-22367
Reviewer: Jason
Tests run: checkintests, Mustella (spark/effects, mx/effects/Sequence)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22367
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

[svn:fx-trunk] 13201: Fix RTE when calling PopUpManager.createPopUp() from a module or sub-application.

Revision: 13201
Revision: 13201
Author:   [email protected]
Date:     2009-12-23 12:16:41 -0800 (Wed, 23 Dec 2009)
Log Message:
Fix RTE when calling PopUpManager.createPopUp() from a module or sub-application.
This fix adds a moduleFactory parameter to PopUpManager.createPopUp() to allow a module or sub-application to specify the style manager to be used. Modules and sub-applications should always pass a moduleFactory to PopUpManager.createPopUp() or PopUpManager.addPopUp() to ensure the correct style manager is used when looking up styles. Otherwise the parent of the pop up is used to determine the style manager.
QE notes: Please create a PerModuleStyles test that uses the new parameter to createPopUp().
Doc notes: None.
Bugs: SDK-24835.
Reviewer: Alex
Tests run: checkintests, Managers/PopUpManager
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24835
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/IPopUpManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/PopUpManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as

[svn:fx-trunk] 11384: Fix RTE when a module is reloaded.

Revision: 11384
Author:   [email protected]
Date:     2009-11-02 15:28:56 -0800 (Mon, 02 Nov 2009)
Log Message:
Fix RTE when a module is reloaded.
We have multiple style managers now so we need to reload the styles and initialize the protochain root for every new instance of an application or module.
QE notes: None.
Doc notes: None.
Bugs: SDK-23948, SDK-23942
Reviewer: Corey
Tests run: checkintests
Is noteworthy for integration: No.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23948
    http://bugs.adobe.com/jira/browse/SDK-23942
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/gen/ClassDefLib.vm

[svn:fx-trunk] 5837: Fix RTE when running Spark WindowedApplication.

Revision: 5837
Author: [email protected]
Date: 2009-04-01 07:46:58 -0700 (Wed, 01 Apr 2009)
Log Message:
Fix RTE when running Spark WindowedApplication.
The problem was introduced by an error in the rename change. Changed the include for Button from mx.controls.Button to spark.components.Button.
QE Notes: None
Doc Notes: None
Bugs:
Reviewer:
tests: checkintests
Modified Paths:
flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/windowClasses/TitleB ar.as

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

[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] 11999: Fixed: ASC-3889 - Using setting in a for loop causes Verify error

Revision: 11999
Revision: 11999
Author:   [email protected]
Date:     2009-11-19 11:37:09 -0800 (Thu, 19 Nov 2009)
Log Message:
Fixed: ASC-3889 - Using setting in a for loop causes Verify error
Notes: emit pop after callstatic to a void function to balance the stack.
Reviewer: jodyer+
Testing: asc,tamarin,flex checkin tests
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3889
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

Blacklisting the ahci module does indeed get rid of the error. Would be nice to figure out why it was conflicting with the ahci module though.
I have not yet tried the 173xx drivers, but the latest drivers for the Quadro FX 580 are the 256.53 drivers according to nvidia.
Posted at the nV forums (http://www.nvnews.net/vbulletin/showthread.php?t=155282), so we'll see what they suggest.

[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] 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:bz-trunk] 23085: Fix test to explicitly remove an event listener after the test is finished .

Revision: 23085
Revision: 23085
Author:   [email protected]
Date:     2011-10-21 07:49:33 -0700 (Fri, 21 Oct 2011)
Log Message:
Fix test to explicitly remove an event listener after the test is finished. Not doing this was causing the test to throw an RTE.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml

Thanks for the ideas regarding beforeInvoke, Ben. I will try to check that out. In my situation, here's essentially how my script is working...
BeforeSave is invoked.
Script makes a change to the document, which should be captured in the saved file.
Document saves.
Document appears saved for a moment, and then appears unsaved (asterisk in the document title).
My biggest problem is that this behavior isn't consistent. I have dozens of users, all running the same script, and the problem only occurs with certain users and at random times. I can move a problematic document from a user's machine to a different machine, and the problem doesn't occur there. It's very difficult to troubleshoot because I can't reproduce it consistently.

[svn:fx-trunk] 13257: Fix for @inheritDoc not working on a setter, but works on a getter

Revision: 13257
Revision: 13257
Author:   [email protected]
Date:     2010-01-04 10:49:13 -0800 (Mon, 04 Jan 2010)
Log Message:
Fix for @inheritDoc not working on a setter, but works on a getter
QE notes: None.
Doc notes: None
Bugs: SDK-24727
Reviewed By: Paul
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24727
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java

steabert wrote:
Hi,
I had a similar problem with my Dell Latitude E4310, and apparently also the E6410, E6510.
The solution for me was to add the following line to /etc/modprobe.d/modprobe.conf:
options snd-hda-intel model=dell-s14
I tried that, unfortunately it does not work with this chipset. I do get a different set of channels though but it still cannot record anything. Maybe this chipset is too "new" for alsa. The latest release dates back from the end of January. Support for it is explicitly stated in the changelog to 1.0.24 but perhaps the recording part of it slipped through the cracks. ALSA bug tracking system seems quite closed.

[svn:fx-trunk] 12685: Fix for RTE in VideoPlayer when trying to capture bitmaps.

Revision: 12685
Revision: 12685
Author:   [email protected]
Date:     2009-12-08 19:23:32 -0800 (Tue, 08 Dec 2009)
Log Message:
Fix for RTE in VideoPlayer when trying to capture bitmaps. Put try-catch block around bitmapData.draw() and use a Rectangle if it throws an error. Also, added some documentation in BitmapUtil for getSnapshot since it may throw the same type of error.
QE notes: No
Doc notes: No
Bugs: SDK-24574
Reviewer: Ryan
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24574
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/HighlightBitmapCaptureSkin .as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/utils/BitmapUtil.as

[svn:fx-trunk] 5812: Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information , so the animation would skip immediately to the end.

Revision: 5812
Author: [email protected]
Date: 2009-03-31 11:34:56 -0700 (Tue, 31 Mar 2009)
Log Message:
Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information, so the animation would skip immediately to the end.
Bugs: SDK-20356
QE Notes: spark/effects Mustella tests currently hosed, couldn't run test suite
Doc Notes: None
Reviewer: Jason
Testing: checkintests, Mustella effects tests could not be run (post-rename issues)
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-20356
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/AnimationProperty.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/animation/Animation.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateColorIns tance.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateShaderTr ansitionInstance.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/FadeInstance.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/MoveInstance.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/ResizeInstance. as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/Rotate3DInstanc e.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/RotateInstance. as

Hi
Can you please try setting up full persmission in the security properties for everyone on the wsconfig folder C:\ColdFusion10\config\wsconfig and restart ColdFusion Server.
Swaraj

[svn:fx-trunk] 8024: Fixed an injection where setting the 'content' property of Spark text component to a TextFlow would cause you to get a TextFlow nested inside a TextFlow .

Revision: 8024
Author:   [email protected]
Date:     2009-06-19 16:59:25 -0700 (Fri, 19 Jun 2009)
Log Message:
Fixed an injection where setting the 'content' property of Spark text component to a TextFlow would cause you to get a TextFlow nested inside a TextFlow.
QE Notes: None
Doc Notes: None
Bugs: SDK-21906
Reviewer: Carol to review
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21906
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/RichText.as

Well, I've already solved one of the two issues
In order to display the icons on my buttonbar buttons, I just needed to point at {hostComponent.data.data} instead of {hostComponent.data}. I'm not sure why, but {hostComponent.data} in my skin class is a handle on my instance of ButtonBarButton, not its "data" property. Any explanation is welcomed
I still have got the first issue though. Oddly enough my design works if I put an mx Image instead of the spark BitmapImage for the client logo. That will do the trick for the moment but I'd prefer to deliver a 100% pure spark component in my prototype, and I can see no reason why BitmapImage works inside my ButtonBarButtons and doesn't otherwise...

[svn:fx-trunk] 8602: Fix RTE after setting baseColor.

Similar Messages

Maybe you are looking for