[svn:osmf:] 17565: Fix FM-937: ProxyElement dispatches trait events for blocked and overridden traits.

Revision: 17565
Revision: 17565
Author:   [email protected]
Date:     2010-09-02 17:30:08 -0700 (Thu, 02 Sep 2010)
Log Message:
Fix FM-937: ProxyElement dispatches trait events for blocked and overridden traits. Add unit test.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-937
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ProxyElement.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestProxyElement.as

Similar Messages

[svn:osmf:] 14592: Fix bug in ProxyElement's blockedTraits implementation.

Revision: 14592
Revision: 14592
Author:   [email protected]
Date:     2010-03-04 16:13:02 -0800 (Thu, 04 Mar 2010)
Log Message:
Fix bug in ProxyElement's blockedTraits implementation. Blocked traits take precedence over overridden traits. The bug was that events would still be dispatched for an overridden trait being added even when the trait was blocked. Update unit tests.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ProxyElement.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestProxyElementAsDynamicProxy.as

(Removed)

[svn:osmf:] 15527: Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified .

Revision: 15527
Revision: 15527
Author:   [email protected]
Date:     2010-04-16 17:21:06 -0700 (Fri, 16 Apr 2010)
Log Message:
Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified. Updated unit tests.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-696
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaPlayer.as

Major Update: The G-Keys can now be edited without recompiling by editing shell scripts at "/usr/share/g15daemon/macros/"
Each button has it's own script file named by it's label (e.g. to edit the functionality of G1, open the script named G1.) The button will try to execute the scripts as programs, so make sure they are executable (chmod +x) and as long as the name remains the same, if you want to replace the files with something different, know that the arguments currently given to the files ($1 and $2) are ($1)on/off and ($2)0-2 (where 0 is M1 and 2 is M3)
To download the updated sources, go here (only the g15daemon source/patch was updated). This thread's OP has been updated.
Last edited by rabcor (2015-02-12 04:46:48)

[svn:osmf:] 12656: Fix bug FM-257: Rename durationReached event type to complete.

Revision: 12656
Revision: 12656
Author:   [email protected]
Date:     2009-12-08 09:45:59 -0800 (Tue, 08 Dec 2009)
Log Message:
Fix bug FM-257: Rename durationReached event type to complete. Also, updated unit tests to be in sync with latest changes (including loc work).
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-257
Modified Paths:
    osmf/branches/flex4/framework/MediaFramework/org/osmf/composition/CompositeTemporalTrait. as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/events/TimeEvent.as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/media/MediaPlayer.as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/proxies/ListenerProxyElement.as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/proxies/TemporalProxyElement.as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/traits/ITemporal.as
    osmf/branches/flex4/framework/MediaFramework/org/osmf/traits/TemporalTrait.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/audio/TestAudioTemporalTrai t.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/composition/TestCompositeMe tadata.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelEle ment.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelSwi tchableTrait.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialEleme nt.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/content/TestContentLoader.a s
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/image/TestImageLoader.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaPlayer.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestMetadata.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestMetadataUtils. as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/net/dynamicstreaming/TestDy namicStreamingResource.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/plugin/TestDynamicPluginLoa der.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/swf/TestSWFLoader.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/traits/TestLoaderBase.as
    osmf/branches/flex4/framework/MediaFrameworkFlexTest/org/osmf/traits/TestTemporalTrait.as
    osmf/branches/flex4/libs/VAST/org/osmf/vast/media/VASTImpressionProxyElement.as
    osmf/branches/flex4/libs/VAST/org/osmf/vast/media/VASTTrackingProxyElement.as

[svn:osmf:] 17497: Fix FM-933: ProxyMetadata doesn' t dispatch change events for its initially set inner metadata.

Revision: 17497
Revision: 17497
Author:   [email protected]
Date:     2010-08-27 09:58:09 -0700 (Fri, 27 Aug 2010)
Log Message:
Fix FM-933: ProxyMetadata doesn't dispatch change events for its initially set inner metadata.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-933
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/LoadFromDocumentElement.as
    osmf/trunk/framework/OSMF/org/osmf/elements/ProxyElement.as
    osmf/trunk/framework/OSMF/org/osmf/elements/proxyClasses/ProxyMetadata.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestProxyElement.as

[svn:osmf:] 12986: Integrate refactored composite view trait ( merger of view and spatial traits).

Revision: 12986
Revision: 12986
Author:   [email protected]
Date:     2009-12-15 23:31:57 -0800 (Tue, 15 Dec 2009)
Log Message:
Integrate refactored composite view trait (merger of view and spatial traits). Implementation is untested, unit tests still to be refactored.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/CompositeMediaTraitFactory.as
Added Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/CompositeViewTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/ParallelViewTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/SerialViewTrait.as

[svn] 4707: Dispatch propertyChange event for horizontalScrollPosition/ verticalScrollPosition so the thumbnail in the scroller will track the movement made via the keyboard .

Revision: 4707
Author: [email protected]
Date: 2009-01-28 09:00:45 -0800 (Wed, 28 Jan 2009)
Log Message:
Dispatch propertyChange event for horizontalScrollPosition/verticalScrollPosition so the thumbnail in the scroller will track the movement made via the keyboard.
QE Notes:
Doc Notes:
Bugs: SDK-18887
Reviewers: Gordon
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18887
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/TextView.as

Revision: 4707
Author: [email protected]
Date: 2009-01-28 09:00:45 -0800 (Wed, 28 Jan 2009)
Log Message:
Dispatch propertyChange event for horizontalScrollPosition/verticalScrollPosition so the thumbnail in the scroller will track the movement made via the keyboard.
QE Notes:
Doc Notes:
Bugs: SDK-18887
Reviewers: Gordon
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18887
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/TextView.as

Flex 4 does not dispatch keyboard events for ENTER key.

Hello everyone. I think I have a strange problem with Flex 4 Beta (4.0.0.8909). My application has had event listener for keyUp event for a month now and suddenly (two days ago) I've noticed that keyUp event is not dispatched for ENTER (ALT also) key. Anyone know why? By the way, I've tried this with keyDown event, also 4.0.0.8847 version of SDK - still the same: no keyboard events for ENTER (and ALT) key.
Here is the sample application that has got this issue:
<s:Application
   xmlns:fx="http://ns.adobe.com/mxml/2009"
   xmlns:s="library://ns.adobe.com/flex/spark"
   xmlns:mx="library://ns.adobe.com/flex/halo"
   minWidth="640" minHeight="480"
   keyUp="application1_keyUpHandler (event)">
   <fx:Script>
      <![CDATA[
         import mx.controls.Alert;
         protected function application1_keyUpHandler (event: KeyboardEvent):void
            Alert.show ("Key up: " + event.keyCode);
      ]]>
   </fx:Script>
   <s:layout>
      <s:BasicLayout/>
   </s:layout>
   <s:TextArea verticalCenter="0" horizontalCenter="0" width="200"/>
</s:Application>
If you run this application and try typing anything in a TextArea you will get alerts with key codes. However, if you press ENTER (or ALT), you will get no alert.
I'm pretty sure the code above is right so that means there is a bug in latest nightly builds of SDK (i would swhitch to an older build if i knew which one does not have this bug).
Any ideas?

Flex harUI wrote:
That's true, but in this case, I think the text editing code is eating ENTER key in order to prevent parents from seeing it and acting on it (like a submit button). We'll see if we can find a way around that.
You can get the ENTER key now by listening in capture phase.
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
The enter key isn't being disposed of by textedit, the attached example code works without error if you a- remove the alert box and b-set the focus to your text area on initialisation. I agree that pressing the enter key then calling a dialog box will result in the enter key being "gobbled up" as the enter key is overridden by the dialog box code.
I think the first suggestion should be to anyone don't use dialogboxes for testing code. If for some reason debugging isn't desirable instead of a trace statement a simple label can be used as a 'fake' trace.
David
Message was edited by: David_F57: I worded this wrong, imho there is no need for a work around, the textarea component works as it should. When intercepting 'system' keycodes there is a need to consider the effect of the intercept and code appropriately to that end.

[svn:osmf:] 15196: Fix bug FM-621: SerialElement dispatches READY event twice.

Revision: 15196
Revision: 15196
Author:   [email protected]
Date:     2010-04-01 21:16:48 -0700 (Thu, 01 Apr 2010)
Log Message:
Fix bug FM-621: SerialElement dispatches READY event twice. Fix inconsistency between MediaPlayer.stop implementation and ASDoc (i.e. the method should always rewind). Temporarily disable DurationElement test, needs some investigation as to why it behaves so different from the other MediaElement-in-MediaPlayer tests.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-621
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/SerialSeekTrait.as
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaPlayer.as

[svn:osmf:] 11205: Fix bug FM-169: Trait support for data transfer sample doesn' t display bytes loaded and bytes total for SWF element

Revision: 11205
Author:   [email protected]
Date:     2009-10-27 15:04:26 -0700 (Tue, 27 Oct 2009)
Log Message:
Fix bug FM-169: Trait support for data transfer sample doesn't display bytes loaded and bytes total for SWF element
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-169
Modified Paths:
    osmf/trunk/apps/samples/framework/PluginSample/src/PluginSample.mxml
    osmf/trunk/apps/samples/framework/PluginSample/src/org/osmf/model/Model.as

The bug is known, and a patch has been submitted: https://bugs.freedesktop.org/show_bug.cgi?id=80151. There's been no update since friday, so I wonder what the current status is, or if it's up for review at all.
Does anyone know how we can be notified when this patch hits the kernel?

[svn:osmf:] 14871: Fixing anchoring 'right' and 'bottom' properties not being applied on items that don't have a width/ height and position set.

Revision: 14871
Revision: 14871
Author:   [email protected]
Date:     2010-03-19 01:05:54 -0700 (Fri, 19 Mar 2010)
Log Message:
Fixing anchoring 'right' and 'bottom' properties not being applied on items that don't have a width/height and position set.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutRenderer.as

If you're just doing it in a back and forth or spiral fashion, you don't need to check whether a square's been filled in. You just go from a start point to an end point. Those points and the squares in between are determined by simple arithmetic.
If you're doing it randomly, I wouldn't use the GUI elements themselves. I'd have, for example, and array of booleans that tells whether each square has been filled in.

[svn:osmf:] 15769: Fix FM-505 - Document behavior of F4MElement ( and LoadFromDocumentElement) with regard to trait events.

Revision: 15769
Revision: 15769
Author:   [email protected]
Date:     2010-04-27 13:59:03 -0700 (Tue, 27 Apr 2010)
Log Message:
Fix FM-505 - Document behavior of F4MElement (and LoadFromDocumentElement) with regard to trait events.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-505
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/F4MElement.as
    osmf/trunk/framework/OSMF/org/osmf/elements/LoadFromDocumentElement.as

[svn:osmf:] 15121: Fix bug related to validation of plugin versions.

Revision: 15121
Revision: 15121
Author:   [email protected]
Date:     2010-03-29 17:33:12 -0700 (Mon, 29 Mar 2010)
Log Message:
Fix bug related to validation of plugin versions. The fix is to load a dynamic plugin SWF twice. The first time it's loaded into a separate ApplicationDomain, so that the class types are not merged (and Version.version will not have identical values for player and plugin). If the version types are consistent, then the plugin is loaded a second time, this time into the same SecurityDomain (so that class types are merged). The second load should pull the SWF from the cache, minimizing the overhead. The downside is that the SWF will be initialized twice.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/SWFLoader.as
    osmf/trunk/framework/OSMF/org/osmf/elements/loaderClasses/LoaderUtils.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/DynamicPluginLoader.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/PluginLoader.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/media/pluginClasses/TestPluginManagerIn tegration.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/utils/IntegrationTestUtils.as

Hi sebasvideo, Did you ever find a solution to this? I've been having the same problem for a few months now and it's maddening. Seems to be specific to the GPU like you say above. I noticed it most when using Element 3D. I thought maybe there was some sort of read/write interference as I have 2 SSDs and one HD with assets spread across all of them. But even when I consolidated all of my data to one drive the flickering kept happening. Not sure if it's an After Effects problem specifically... or windows 8.1? Or nVidia? Super frustrating thoguh.

[svn:osmf:] 13028: Fix bug where NetStream would continue playback upon completion ( due to our not handling the new STOPPED state).

Revision: 13028
Revision: 13028
Author:   [email protected]
Date:     2009-12-16 18:10:28 -0800 (Wed, 16 Dec 2009)
Log Message:
Fix bug where NetStream would continue playback upon completion (due to our not handling the new STOPPED state). Injection from trait refactoring.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamPlayTrait.as

My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

[svn:osmf:] 13967: Fix a bug where flushing doesn' t happen right at end-of-playback

Revision: 13967
Revision: 13967
Author:   [email protected]
Date:     2010-02-03 16:35:08 -0800 (Wed, 03 Feb 2010)
Log Message:
Fix a bug where flushing doesn't happen right at end-of-playback
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/HTTPNetStream.as

Dear Adobe support team,
It's quite an old thread however no update fix for this issue but the workarounds of the good people above. This tiny and yet very irritating bug should has been fixed a long time ago in an update patch. I'm using the latest version of Premiere Pro CS6 (6.0.5) and still look forward for an update fix. I haven't checked whether this issue exists in the CC edition of Premiere Pro, however even if it has been fixed there, I'm not willing to upgrade to it no matter what as I believe in a product I paid the full price for ONCE and that should receive its yearly bug-fix updates, and not for one with an annual fee.
I look forward to hearing from you.
Thanks,
Gal Shemesh

[svn:osmf:] 17565: Fix FM-937: ProxyElement dispatches trait events for blocked and overridden traits.

Similar Messages

Maybe you are looking for