[svn:fx-trunk] 10831: Fix for databound state-specific values.

Revision: 10831
Author:   [email protected]
Date:     2009-10-02 12:01:39 -0700 (Fri, 02 Oct 2009)
Log Message:
Fix for databound state-specific values.
QE notes: None
Doc notes: None
Bugs: SDK-23525
Reviewer: Paul
Tests run: Checkin, States (Mustella)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23525
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/StatesModel.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitializer.ja va

Similar Messages

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

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

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

[svn:fx-trunk] 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] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Revision: 12962
Revision: 12962
Author:   [email protected]
Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for ASDoc not saving event type for metadata tag
QE notes: None.
Doc notes: None
Bugs: SDK-24706
Reviewed By:Corey
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24706
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
Which correspondents fine with the
device "hw:0,3"
in my mpd.conf alsa section.
Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
hokasch:
I tried changing the mixer to "Master" but that did not change much.

[svn:fx-trunk] 7473: Fix for 'ant asdoc' does not work.

Revision: 7473
Author:   [email protected]
Date:     2009-06-01 12:09:26 -0700 (Mon, 01 Jun 2009)
Log Message:
Fix for 'ant asdoc' does not work.
It should now work from both svn and package zip.
Bugs: SDK-15306
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15306
Modified Paths:
    flex/sdk/trunk/asdoc/build.xml
    flex/sdk/trunk/build.xml

[svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

Revision: 13136
Revision: 13136
Author:   [email protected]
Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
Log Message:
Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXENT-1196
Modified Paths:
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

[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] 12982: Fix for issue with exposing accessible names for combobox list items

Revision: 12982
Revision: 12982
Author:   [email protected]
Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for issue with exposing accessible names for combobox list items
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

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

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[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] 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] 14139: Fix for Player classes not code hinting to framework FB projects.

Revision: 14139
Revision: 14139
Author:   [email protected]
Date:     2010-02-11 16:36:39 -0800 (Thu, 11 Feb 2010)
Log Message:
Fix for Player classes not code hinting to framework FB projects. Changed all the $ tokens to use $ instead. While the compiler understands $, Flash Builder's code model does not.
No code changes.
QE notes: N/A
Doc notes: N/A
Bugs: None
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airspark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/flex/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/framework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/osmf/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/rpc/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/spark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.actionScriptProperties

[svn:bz-trunk] 17920: Fix for WebLogic: WebLogic does not provide File IO on the deployed artifacts hence using getResourceAsStream .

Revision: 17920
Revision: 17920
Author:   [email protected]
Date:     2010-09-29 05:56:06 -0700 (Wed, 29 Sep 2010)
Log Message:
Fix for WebLogic: WebLogic does not provide File IO on the deployed artifacts hence using getResourceAsStream.
Modified Paths:
    blazeds/trunk/apps/samples/WEB-INF/src/flex/samples/marketdata/Portfolio.java

check the server log;
/app/oracle/product/fwm11g/user_projects/domains/fwm_domain/servers/AdminServer/logs/AdminServer.log
you can launch the console and see if it is running; http://<server>:<port>/console

[svn:fx-trunk] 14017: Fix for icons being off-center in the wireframe CheckBox and RadioButton.

Revision: 14017
Revision: 14017
Author:   [email protected]
Date:     2010-02-05 16:16:37 -0800 (Fri, 05 Feb 2010)
Log Message:
Fix for icons being off-center in the wireframe CheckBox and RadioButton. The icon was not being vertically centered.
QE notes: No
Doc notes: No
Bugs: SDK-25304
Reviewer: Jason
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25304
Modified Paths:
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/CheckBoxSkin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/RadioButtonSkin.mx ml

Welcome guy -
Unless you are using Spry menus as a learning experience, you should move forward to a menus system that will display properly on the millions of portable devices that won't work with Spry which was deprecated 2 years ago.
Many are using JQuery menus or pure HTML/CSS menus.
If you wish to continue your Spry for learning experience, we'll be glad to assist; please let us know.
By the way, your submenus are not showing because you need to add the red value to this rule in your vertical CSS
ul.MenuBarVertical ul.MenuBarSubmenuVisible{
    width: 220px;
    left: 180px;

[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] 10831: Fix for databound state-specific values.

Similar Messages

Maybe you are looking for