[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;
Similar Messages
-
Revision: 13317
Revision: 13317
Author: [email protected]
Date: 2010-01-06 16:19:04 -0800 (Wed, 06 Jan 2010)
Log Message:
Fix to allow Animate to automatically handle changes in styles during transitions. This same logic already works for properties (e.g., if you specify different values for x in states and run Animate with a SimpleMotionPath with property="x" then it will automatically determine the from/to values to animate for x). But we needed to add an override for getRelevantStyles() for Animate to advertise the possible styles to pick up changes for so that the transitions array would be populated accordingly.
QE notes: None
Doc notes: This is a fix that should allow the second animated skin example in the docs (spark_skinning, p46) to work as detailed in my edits
Bugs: sdk-24932
Reviewer: Jason
Tests run: checkintests, Mustella spark/effects
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/sdk-24932
Modified Paths:
flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Animate.asFYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989
-
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.xmlThats good news.
-
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] 12078: Fix for change events in Slider and ScrollBar.
Revision: 12078
Revision: 12078
Author: [email protected]
Date: 2009-11-21 00:14:46 -0800 (Sat, 21 Nov 2009)
Log Message:
Fix for change events in Slider and ScrollBar. They now dispatch change events as before, whenever the user alters the value. In addition, changeStart and changeEnd events will be dispatched at the start and end of a user interaction or animation.
TrackBase.as - Added metadata for changeStart/End events. Dispatch change, changeStart/End events when appropriate.
Slider.as - Dispatch change, changeStart/End events when appropriate.
ScrollBar.as - Dispatch the appropriate events. Note that changeStart/End will not dispatch when shift-clicking on a non-animating ScrollBar. Renamed animatingSinglePage to animatingOnce to better reflect its function. Refactored some method calls to the new private stopAnimation(), which is more consistent with Slider. Refactored the button handlers to make stepping more readable. Added a setValue call in animationEndHandler where we were ending up off the snapInterval when shift-clicking.
Updated FlexEvent, ScrollBarTestScript and VideoPlayer to handle the new events.
QE notes: Update Slider and ScrollBar tests
Doc notes: No
Bugs: SDK-24264
Reviewer: Ryan
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-24264
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/events/FlexEvent.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ScrollBar.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/TrackBase.as
flex/sdk/trunk/frameworks/tests/basicTests/spark/scripts/ScrollBarTestScript.mxml -
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.asAdd 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; -
Revision: 9328
Author: [email protected]
Date: 2009-08-14 17:02:35 -0700 (Fri, 14 Aug 2009)
Log Message:
Fixing SDK-22462: Event dispatched is not as expected in Tree
For this, the issue is really that TreeItemRenderers assume that no click event can occur on the disclosureIcon. This is because the discolsureIcon is added and removed each time it goes through invalidation in commitProperties(), so a new discolsureIcon gets created and replaces the old one after they mouseDown (meaning no click event actually occurs). Automation replays some mouse events on one disclosureIcon only (which is an automation bug because that?\226?\128?\153s not how it actually works in the real world) and when a ?\226?\128?\156click?\226?\128?\157 occurs, that causes an itemClick on the Tree, when it shouldn?\226?\128?\153t. For Flex 3, this wasn?\226?\128?\153t a problem because the IR was getting invalidated through a different codepath because openDuration did not default to 0. If you set it to 0, you?\226?\128?\153d see the same problem in Flex 3. Anyways, the fix is just to block all click events that occur on the disclosureIcon.
QE notes: -
Doc notes: -
Bugs: SDK-22462
Reviewer: Alex
Tests run: checkintests, mustella Tree
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-22462
http://bugs.adobe.com/jira/browse/SDK-22462
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/treeClasses/TreeItemRenderer .aserror dateField not selecion date 27/11/2002 ?
This is bug flex 3 ?
thanks -
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.vmFYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989
-
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: 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. -
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.javaRevision: 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: 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.asAgree 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. -
[svn:bz-trunk] 9665: Fix minor typo in errors.properties file.
Revision: 9665
Author: [email protected]
Date: 2009-08-26 14:13:27 -0700 (Wed, 26 Aug 2009)
Log Message:
Fix minor typo in errors.properties file. Change "wilcard" to "wildcard" in the following error string.
10560=Attempt to subscribe to the subtopic, '''', on destination, '''', that does not allow wilcard subtopics failed.
Checkintests: passed
Modified Paths:
blazeds/trunk/modules/common/src/flex/messaging/errors.properties
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/dynamicDestinat ions/subtopicsEnabledWildcardsNotAllowed.mxmlonearm wrote:
Svn revision 442 doesn't compile on Arch64:
[ 4%] [ 5%] Building CXX object src/CMakeFiles/guayadeque.dir/AlListBox.o
Building CXX object src/CMakeFiles/guayadeque.dir/ArListBox.o
In file included from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/LastFMPanel.h:25,
from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/MainFrame.h:27,
from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/AlListBox.cpp:27:
/tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/PlayerPanel.h:25:28: error: AutoScrollText.h: No such file or directory
[ 7%] Building CXX object src/CMakeFiles/guayadeque.dir/ArrayStringArray.o
[ 8%] Building CXX object src/CMakeFiles/guayadeque.dir/AudioScrobble.o
make[2]: *** [src/CMakeFiles/guayadeque.dir/AlListBox.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [src/CMakeFiles/guayadeque.dir/all] Error 2
make: *** [all] Error 2
Thanks for the bug report. It was a test i was doing but finally decided to not include it but left this line by error.
It have been fixed in svn 443.
Thanks again -
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] 11602: Fix for Button tooltips.
Revision: 11602
Author: [email protected]
Date: 2009-11-09 22:35:11 -0800 (Mon, 09 Nov 2009)
Log Message:
Fix for Button tooltips. TextBase dispatches an event when _isTruncated is set through the setIsTruncated() function. This allows ButtonBase to listen for the event and set the tooltip as necessary. If an explicit tooltip is set, then ButtonBase will not set a tooltip.
QE notes: No
Doc notes: No
Bugs: SDK-22260, SDK-23474, SDK-23657
Reviewer: Evtim
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-22260
http://bugs.adobe.com/jira/browse/SDK-23474
http://bugs.adobe.com/jira/browse/SDK-23657
Modified Paths:
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ButtonBase.a s
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/TextBase.as
Maybe you are looking for
-
I recently upgraded to Yosemite. Yesterday when I opened up the iPhoto (which I have it in my external drive due to the size of file) I get the message that it is not compatible with the new system(or something like that) and ask me to upgrade so I d
-
Hi, What are the steps required for the database backups to be taken on tape drives ? Is rman sufficient for that? thanks..
-
Has anyone else's weather animations stopped moving??
Has anyone else's weather animations stopped moving?? I have just upgraded to the iPhone 6 Plus with IOS 8.1.
-
Hi, Can anybody explain total how many G/l Accounts, we will generally assign and please give the list including TE Key.. The reply will be highly appreciated...
-
ITunes generates "com.apple.iTunes.plist" file after each start up
On one of our Mac's after each startup of iTunes a file is generated in /Users/Name/Library/Preferences File names are like: com.apple.iTunes.plist.Z2buKbR com.apple.iTunes.plist.lx6pQwr com.apple.iTunes.plist.0YWqm3c File size is zero (0) How can I