[svn:fx-trunk] 11926: Fix 3. 0 compatiblity-version bug with generated styles.

Revision: 11926
Revision: 11926
Author:   [email protected]
Date:     2009-11-18 04:46:03 -0800 (Wed, 18 Nov 2009)
Log Message:
Fix 3.0 compatiblity-version bug with generated styles.
src/java/flex2/compiler/common/CompilerConfiguration.java
   Turn ?\226?\128?\147isloate-styles off in 3.0 compatibility mode. This flag also turns on the hidden option ?\226?\128?\147allow-duplicate-default-style-declarations which is what fixes the bug.
src/java/flex2/compiler/css/StyleDef.vm
   Changed a tab to spaces.
QE notes: None.
Doc notes: None.
Bugs: SDK-24259
Reviewer: Peter
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24259
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/CompilerConfiguration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.vm

FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

Similar Messages

[svn:fx-trunk] 6993: * Fixed a duplicate Bindable metadata bug that showed up with

Revision: 6993
Author:   [email protected]
Date:     2009-05-16 23:57:42 -0700 (Sat, 16 May 2009)
Log Message:
Fixed a duplicate Bindable metadata bug that showed up with
describeType().
tests Passed: checkintests
Needs QA: YES, just confirm the bug fix, please.
Needs DOC: NO
Bug fixes: SDK-21133
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
BindableSecondPassEvaluator.java
    Modified moveMetaDataToNewDefinition() to no longer insert the new
    Bindable metadata into the definition's statement list, because
    prepMetaDataNode() already handles this.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21133
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java

I just noticed that for some reason the project is using an old path to my SVN repository. I recreated it and reimported the project but for some reason Xcode didn't realize that. I'm betting there's some little file somewhere that's causing my problem.

[svn:fx-trunk] 5802: Fix ant asdoc target to work with the new manifest files.

Revision: 5802
Author: [email protected]
Date: 2009-03-31 09:14:44 -0700 (Tue, 31 Mar 2009)
Log Message:
Fix ant asdoc target to work with the new manifest files.
QE Notes: None.
Doc Notes: None.
tests: checkintests
Modified Paths:
flex/sdk/trunk/asdoc/build.xml

Thats good news.

[svn:bz-trunk] 19423: Fixes blz-604 BlazeDS samples error with "Error #1014 : Class flash.events::SoftKeyboardEvent could not be found."

Revision: 19423
Revision: 19423
Author:   [email protected]
Date:     2010-12-16 07:00:31 -0800 (Thu, 16 Dec 2010)
Log Message:
Fixes blz-604 BlazeDS samples error with "Error #1014: Class flash.events::SoftKeyboardEvent could not be found."
Ticket Links:
    http://bugs.adobe.com/jira/browse/blz-604
Modified Paths:
    blazeds/trunk/qa/resources/webtier/flex_sdk_4/flex-config.xml

[svn:fx-trunk] 8909: * Fix to allow Script blocks interspersed with default property

Revision: 8909
Author:   [email protected]
Date:     2009-07-29 13:19:07 -0700 (Wed, 29 Jul 2009)
Log Message:
Fix to allow Script blocks interspersed with default property
children.
QE notes:
Doc notes:
Bugs: SDK-22249
Reviewer: Pete F.
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22249
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/ChildNodeHandler.java

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] 12207: Fix for [Managed] metadata prevents ASDoc from generating output for setter/getters

Revision: 12207
Revision: 12207
Author:   [email protected]
Date:     2009-11-25 11:53:15 -0800 (Wed, 25 Nov 2009)
Log Message:
Fix for metadata prevents ASDoc from generating output for setter/getters
QE notes: None
Doc notes: None
Reviewed By: Paul
Bugs: SDK-23940
Tests run: checkintests, asdoc
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23940
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeSecondPassEv aluator.java

[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] 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] 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] 7891: Fixed bug in effects that was fallout from renaming offsets property to postLayoutTransformOffsets .

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.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] 5499: Fix TH-3887: [Windows Only] Default system browser preference is ignored at runtime.

Revision: 5499
Author: [email protected]
Date: 2009-03-23 14:59:54 -0700 (Mon, 23 Mar 2009)
Log Message:
Fix TH-3887: [Windows Only] Default system browser preference is ignored at runtime.
Fix SDK-19781: FDB 'run' fails with StringIndexOutOfBoundsException on Windows, if command processor produces AutoRun output.
Ticket Links:
http://bugs.adobe.com/jira/browse/TH-3887
http://bugs.adobe.com/jira/browse/SDK-19781
Modified Paths:
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/DefaultDebuggerCallbacks.ja va
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/IDebuggerCallbacks.java

Revision: 5499
Author: [email protected]
Date: 2009-03-23 14:59:54 -0700 (Mon, 23 Mar 2009)
Log Message:
Fix TH-3887: [Windows Only] Default system browser preference is ignored at runtime.
Fix SDK-19781: FDB 'run' fails with StringIndexOutOfBoundsException on Windows, if command processor produces AutoRun output.
Ticket Links:
http://bugs.adobe.com/jira/browse/TH-3887
http://bugs.adobe.com/jira/browse/SDK-19781
Modified Paths:
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/DefaultDebuggerCallbacks.ja va
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/IDebuggerCallbacks.java

[svn:osmf:] 17638: To fix FM-1040, we came up with a solution as depicted by SVN change number 17636.

Revision: 17638
Revision: 17638
Author:   [email protected]
Date:     2010-09-09 16:34:17 -0700 (Thu, 09 Sep 2010)
Log Message:
To fix FM-1040, we came up with a solution as depicted by SVN change number 17636. However we are not totally satisfied because some multicast specific code was introduced to the NetLoader class. To remedy the problem, we introducted an indirection such that the multicast specific code goes to the MulticastNetLoader.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1040
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/MulticastNetLoader.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetLoader.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamLoadTrait.as

Agree it is a pain in the but I know that you can use the same bbid on 2 playbooks.
Be a Shepard and not an iSheep.

Is Adobe planning on fixing any of the LION bugs with CS5?

I've been reading a lot about these bugs with Adobe CS5 applications and LION (here's some> http://kb2.adobe.com/cps/905/cpsid_90508.html). A friend had a ton of problems and ended up sending her laptop back because of them (she wasnt able to downgrade to Snow Leopard over Lion with that particular laptop). I just ordered a new imac, and think I'm going to be using my old one for a while if there are all these bugs. I primarily use my mac for Photoshop, Illustrator and InDesign, and if they are going to be problematic that is going to be a big drawback for me. I talked to an employee at Apple this weekend, and he said Adobe is always behind the ball with getting their software up to speed with new operating systems. Which didnt make me feel anybetter. Lion's been out for a while now, and I assume Adobe received the OS way before it was released to the public in order for them to upgrade their apps to make them compatible. Does anyone know what the status is on when the next big Adobe update is going to happen to address these issues?

As to bug fixes, you'd have to ask Adobe that question. I would presume they'll fix at least some of the issues before the next major release, but what specifically they'll do, only Adobe could tell you. Note, though, that most of the issues Adobe publicly acknowledges are pretty minor and/or are present in earlier versions of the CS suite, not 5.5.
Regards.

[svn:osmf:] 15680: This submission tries to address a bug with absolute time support.

Revision: 15680
Revision: 15680
Author:   [email protected]
Date:     2010-04-23 16:36:42 -0700 (Fri, 23 Apr 2010)
Log Message:
This submission tries to address a bug with absolute time support. As a result, it fixes a bunch of bugs as follows:
FM-765, FM-766, FM-776, FM-777, FM-778, FM-779, FM-780
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-765
    http://bugs.adobe.com/jira/browse/FM-766
    http://bugs.adobe.com/jira/browse/FM-776
    http://bugs.adobe.com/jira/browse/FM-777
    http://bugs.adobe.com/jira/browse/FM-778
    http://bugs.adobe.com/jira/browse/FM-779
    http://bugs.adobe.com/jira/browse/FM-780
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/DVRInfo.as
    osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/HTTPNetStream.as
    osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/f4f/HTTPStreamingF4FIndexHandler.as

Have done.... I had also sent a copy of the AB database to support on another case using Snow Leopard. I had hoped it was fixed in Lion.

Version 2.0 is not a compatible version error with synch manager

i've build a synch plugin and i put the dll files in the plug in directory.
when im running the synch plugin and im looking through the logs i get the following error "Version 2.0 is not a compatible version."
i think the problem could happen because im using visual studio and i think it compiles standard with framework 2.0 and im guessing synch manager need framework 1.1. but im not sure?
can anyone help me with this problem??
kind regards,
C. Oude Luttikhuis

yes that error message is actually coming from the .Net Framework you can find more on it <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=521514&SiteID=1">here</a>
For a netpoint 5.9 plugin it would need to be compiled in .Net 1.1, if you only have MS Visual Studio 2005 you might want to look into MSBee which will allow you to compile to 1.1 (but requires a higher developer knowledge) or i know that <a href="http://www.icsharpcode.net/OpenSource/SD/Default.aspx">SharpDevelop</a> is a free IDE that will compile to 1.1 code.

[svn:fx-trunk] 11926: Fix 3. 0 compatiblity-version bug with generated styles.

Similar Messages

Maybe you are looking for