[svn:fx-trunk] 10339: Fix BrowserManager for IE8.

Revision: 10339
Author:   [email protected]
Date:     2009-09-16 22:08:06 -0700 (Wed, 16 Sep 2009)
Log Message:
Fix BrowserManager for IE8. Also upgrade SWFObject with some changes from their code base
QE Notes: Last BrowserManagerTest test case fails in IE8. Updated version sent to Joann.
Doc Notes: None
Bugs: SDK-22941
Reviewer: Corey
API Change: No
Is noteworthy for integration: No
tests: checkintests mustella/browser/DeepLinking
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22941
Modified Paths:
    flex/sdk/trunk/templates/swfobject/history/history.js
    flex/sdk/trunk/templates/swfobject/swfobject.js

Similar Messages

[svn:fx-trunk] 9329: Fixing openDuration on Tree.

Revision: 9329
Author:   [email protected]
Date:     2009-08-14 17:07:31 -0700 (Fri, 14 Aug 2009)
Log Message:
Fixing openDuration on Tree. The issue was that a call to UIComponent.suspendBackgroundProcessing() wasn?\226?\128?\153t being respected by LayoutManager, now that it doesn?\226?\128?\153t use UIComponent.callLater(). The fix was for LayoutManager to look at UIComponentGlobals.callLaterSuspsendCount. There are probably other ways to fix this bug because all the tweening in Tree seems very hokey, but given that UIC.suspendBackgroundProcessing() should be respected by LayoutManager, this seemed like the right fix.
QE notes: We should add tests for openDuration
Doc notes: -
Bugs: SDK-21752
Reviewer: Alex
Tests run: checkintests, mustella Tree
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21752
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/LayoutManager.as

ould wrote:
I have done the hard work for you. My HTPC is pretty barebones so it was relatively easy to roll back all the packages that depend on libjpeg>7 with older versions. I then compiled the xbmc-svn package using that system. Slow downs are gone and I have uploaded the package to hotfile here:
http://hotfile.com/dl/13546051/021f9c9/ … ar.gz.html
This is for 32-bit. You will need the libjpeg6 package from AUR installed. I have tested it on two systems, my main system which has both libjpeg7 and the AUR libjpeg6 installed and on my htpc which has only the libjpeg6 along with the rolled back dependancies. Works good on both systems.
Hope that helps!
Kevin
Thanks ould!! You got it working with libjpeg6 again!
I had to upgrade libcdio again so now I lost dvd support. It's not easy to use the svn version.
If you could compile the build against libcdio 0.80 I'd be forever grateful... If you've got the time.
Last edited by Perre (2009-09-26 17:09:04)

[svn:osmf:] 15607: Partial fix #2 for FM-719.

Revision: 15607
Revision: 15607
Author:   [email protected]
Date:     2010-04-20 12:37:41 -0700 (Tue, 20 Apr 2010)
Log Message:
Partial fix #2 for FM-719. This fix ensures that when seeking in and out of the child of a parallel element, that the play state is updated according to the play state of the composition. For example, if there are two parallel children of duration 10 and 20 seconds, and the parallel element is playing, and you seek from 15 to 5, then the shorter child should resume playback. (And similar for when paused.) Bug detected when verifying the (soon to be checked in) fix for FM-719, and seeking in and out of the section of video where the image should be displayed. Added unit tests for these cases as well.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-719
    http://bugs.adobe.com/jira/browse/FM-719
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/ParallelSeekTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestParallelElementWithSeekTrait.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] 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] 11530: Fix ASC-3790 ( conditional expression in for loop causes verifier error) r=jodyer

Revision: 11530
Author:   [email protected]
Date:     2009-11-06 13:23:05 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix ASC-3790 (conditional expression in for loop causes verifier error) r=jodyer
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3790
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/ConditionalExpressionNode.java

[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] 7553: Fix the default value of the [skinPart] "required" attribute for asdoc.

Revision: 7553
Author:   [email protected]
Date:     2009-06-04 09:32:51 -0700 (Thu, 04 Jun 2009)
Log Message:
Fix the default value of the "required" attribute for asdoc.
Bugs: SDK-21488
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21488
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

${ui:cond( uix.current.isNewRow, 'true', ui:cond( bindings.AddProjectNutsoverleg.value == 1, 'true', 'false' ) ) } notice the '.value' it could also be '.inputValue'.
If not there is also an option to make sure that when the checkbox is empty a value is returned anyways this work like this:
protected void processUpdateModel( DataActionContext ctx )
    //First look for the request parameter
    Object cbInRequest = ctx.getHttpServletRequest().getParameter( "nameofthecheckbox" );
    //We only need to do anything if it was not submitted
    if( cbInRequest == null )
      // Get hold of the Form Bean containing the record
      BindingContainerActionForm updateForm = (BindingContainerActionForm) ctx.getActionForm();
      //Get the binding for our particular column
      JUCtrlAttrsBinding checkBoxBinding = (JUCtrlAttrsBinding)updateForm.get( "nameofthecheckbox" );
      //Reset that explicitly to the *unchecked* value
      checkBoxBinding.setAttribute( 0, new oracle.jbo.domain.Number( 0 ) );
    super.processUpdateModel( ctx );
}Maybe this helps.

[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] 7765: Fixing up some copyrights, adding copyrights, and fixing up some legal-eese for the Flash Component Kit For Flex.

Revision: 7765
Author:   [email protected]
Date:     2009-06-11 15:58:18 -0700 (Thu, 11 Jun 2009)
Log Message:
Fixing up some copyrights, adding copyrights, and fixing up some legal-eese for the Flash Component Kit For Flex.
Also, updating the MXP to get latest changes to base classes.
QE Notes: -
Doc Notes: -
Bugs: SDK-21670
Reviewer: No one (just header updates)
tests: checkintest (seem to fail due to local changes to ScrollBar, which I'm not checking in here)
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21670
Modified Paths:
    flex/sdk/trunk/frameworks/flash-integration/FlexComponentKit.mxp
    flex/sdk/trunk/frameworks/flash-integration/readme.txt
    flex/sdk/trunk/frameworks/projects/flash-integration/FlexComponentKit.mxi
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/Convert Symbol to Flex Component.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/Convert Symbol to Flex Container.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/MakeFlexComponent.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/readme.txt
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/ContainerMovieClip.as
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as

[svn:fx-trunk] 10866: Fix broken links in ASDoc comments for TLFTextInput. as and TextArea.as, and add OverrideBase.as to ASDoc output

Revision: 10866
Author:   [email protected]
Date:     2009-10-05 08:56:44 -0700 (Mon, 05 Oct 2009)
Log Message:
Fix broken links in ASDoc comments for TLFTextInput.as and TextArea.as, and add OverrideBase.as to ASDoc output
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/states/OverrideBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/mx/controls/TLFTextInput.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextArea.as

Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
CSS part:
nav p {
font-size: 90%;
color: #FFC;
text-align: right;
font-weight: bold;
background-color: #090;
padding-top: 5px;
padding-right: 20px;
padding-bottom: 5px;
border-top-width: 2px;
border-top-style: solid;
border-top-color: #060;
HTML part: (bold italic is the part I added)
<body>
<div class="container">
<div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
<header></header>
<nav>
    <p>Home | About Us | Contact Us</p>
</nav>
<div class="sidebar1">
    <ul class="nav">
      <li><a href="#">Green News</a></li>
      <li><a href="#">Green Products</a></li>
      <li><a href="#">Green Events</a></li>
      <li><a href="#">Green Travel</a></li>
      <li><a href="#">Green Tips</a></li>
    </ul>

[svn:fx-trunk] 10339: Fix BrowserManager for IE8.

Similar Messages

Maybe you are looking for