[svn:osmf:] 14007: Partial fix for FM-383: ProxyElement needs to dispatch traitRemove/ traitAdd event pairs when the proxy adds or removes a trait that also exists on the proxied element .

Revision: 14007
Revision: 14007
Author:   [email protected]
Date:     2010-02-05 11:54:43 -0800 (Fri, 05 Feb 2010)
Log Message:
Partial fix for FM-383:  ProxyElement needs to dispatch traitRemove/traitAdd event pairs when the proxy adds or removes a trait that also exists on the proxied element.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-383
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaElement.as
    osmf/trunk/framework/OSMF/org/osmf/proxies/ProxyElement.as
    osmf/trunk/framework/OSMFTest/org/osmf/proxies/TestProxyElementAsDynamicProxy.as

Similar Messages

  • [svn:osmf:] 17499: Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available

    Revision: 17499
    Revision: 17499
    Author:   [email protected]
    Date:     2010-08-27 11:05:22 -0700 (Fri, 27 Aug 2010)
    Log Message:
    Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-990
    Modified Paths:
        osmf/trunk/framework/OSMF/org/osmf/elements/ImageElement.as

    Revision: 17499
    Revision: 17499
    Author:   [email protected]
    Date:     2010-08-27 11:05:22 -0700 (Fri, 27 Aug 2010)
    Log Message:
    Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-990
    Modified Paths:
        osmf/trunk/framework/OSMF/org/osmf/elements/ImageElement.as

  • [svn:osmf:] 16270: Recommitted fix for FM-857: VAST and MAST impressions and tracking events are broken.

    Revision: 16270
    Revision: 16270
    Author:   [email protected]
    Date:     2010-05-20 19:19:57 -0700 (Thu, 20 May 2010)
    Log Message:
    Recommitted fix for FM-857: VAST and MAST impressions and tracking events are broken.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-857
    Modified Paths:
        osmf/trunk/libs/samples/VAST/org/osmf/vast/media/VASTImpressionProxyElement.as
        osmf/trunk/libs/samples/VAST/org/osmf/vast/media/VASTTrackingProxyElement.as
        osmf/trunk/libs/samples/VASTTest/org/osmf/vast/media/TestVASTImpressionProxyElement.as
        osmf/trunk/libs/samples/VASTTest/org/osmf/vast/media/TestVASTTrackingProxyElement.as

  • [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:osmf:] 13002: Some fixes for the composite view trait.

    Revision: 13002
    Revision: 13002
    Author:   [email protected]
    Date:     2009-12-16 13:04:30 -0800 (Wed, 16 Dec 2009)
    Log Message:
    Some fixes for the composite view trait.  Integrated some of the unit tests (though some still break and are commented out).
    Modified 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
        osmf/trunk/framework/MediaFramework/org/osmf/layout/LayoutContextSprite.as
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelElement.as
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElement.as
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/utils/DynamicMediaElement.as
    Added Paths:
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelElementWithV iewTrait.as
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElementWithVie wTrait.as

    It's important to understand what traits are and what they're not:
    Traits are not intended to be generically extensible:  there's a fixed set within the framework (although we may add additional traits in the future, to support new Flash/FMS capabilities).  We experimented with making them fully extensible, but it turned out to be not worth the cost, particularly since there shouldn't be that many traits in a media system.
    Traits represent fundamental characteristics or capabilities of the media in its context.  For example, some media is playable (videos), other media is not (images).
    A trait cannot apply to all media types.  If it could, then there would be no reason to model it as a trait, instead we would model it as part of the MediaElement.  Metadata is a good example of this, in that any MediaElement might have some metadata associated with it, so it wouldn't make sense to make metadata a trait.  Similarly, any MediaElement has the ability to go into fullscreen mode, so I wouldn't model the ability to go fullscreen as a trait.
    On a semi-related note, I'm often asked (inside Adobe and elsewhere) for a technical overview of OSMF.  I've posted the slides that I use for this purpose here:
    https://sourceforge.net/adobe/osmf/wiki/_discuss/thread/d6c3d719/1962/attachment/OSMF%20Ar chitectural%20Building%20Blocks.pdf
    The slides cover the fundamental building blocks of OSMF, things you are likely to use over and over if you're building complex media experiences.  They might shed some light on which different parts of OSMF should be used in which situations.

  • [svn:osmf:] 15899: Attempted fix for unit tests failure.

    Revision: 15899
    Revision: 15899
    Author:   [email protected]
    Date:     2010-05-04 17:21:06 -0700 (Tue, 04 May 2010)
    Log Message:
    Attempted fix for unit tests failure.
    Modified Paths:
        osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as

  • [svn:osmf:] 14625: Reworked fix for FM-506.

    Revision: 14625
    Revision: 14625
    Author:   [email protected]
    Date:     2010-03-08 10:37:29 -0800 (Mon, 08 Mar 2010)
    Log Message:
    Reworked fix for FM-506.  Current time == duration once the video stops, and seek(0) goes to 0.   Handles incorrect duration metadata, as well as audio delay offsets.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-506
    Modified Paths:
        osmf/trunk/framework/OSMF/org/osmf/net/NetStreamTimeTrait.as

  • [svn:osmf:] 10683: Bug fix for SWFElement drawing outside of its bounds causing layout havok.

    Revision: 10683
    Author:   [email protected]
    Date:     2009-09-29 09:29:55 -0700 (Tue, 29 Sep 2009)
    Log Message:
    Bug fix for SWFElement drawing outside of its bounds causing layout havok.   FM-87 and FM-77
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-87
        http://bugs.adobe.com/jira/browse/FM-77
    Modified Paths:
        osmf/trunk/framework/MediaFramework/org/openvideoplayer/content/ContentElement.as

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

  • [svn:fx-trunk] 7716: Partial fix for SDK-21182.

    Revision: 7716
    Author:   [email protected]
    Date:     2009-06-10 08:59:13 -0700 (Wed, 10 Jun 2009)
    Log Message:
    Partial fix for SDK-21182. We now set the default compatibility version to the current version and thus the compatibility version string will no longer be null by default (but would be the current version if no override was set). This also means the compiler now matches the ActionScript FlexVersion class.
    This change does not address the issue of revision/minor/major-version fallback in order to select the next most appropriate defaults-x.y.z.css file for any given version.
    Also updated flex-jars eclipse project classpath to reflect recent Batik jar consolidation.
    QE: Yes, if we didn't previously, please change any negative test cases that were checking for --compatibility-version=4 as this is still valid (and is the default).
    Doc: No
    Checkintests: Pass
    Reviewer: Paul
    Bugs:
    SDK-21182 - Fix logic surrounding compatibility version and SWC default.css selection during PreLink
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21182
        http://bugs.adobe.com/jira/browse/SDK-21182
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.java

  • [svn:fx-3.x] 7715: Partial fix for SDK-21182.

    Revision: 7715
    Author:   [email protected]
    Date:     2009-06-10 08:54:33 -0700 (Wed, 10 Jun 2009)
    Log Message:
    Partial fix for SDK-21182. We now set the default compatibility version to the current version and thus the compatibility version string will no longer be null by default (but would be the current version if no override was set). This also means the compiler now matches the ActionScript FlexVersion class.
    This change does not address the issue of revision/minor/major version fallback in selecting the next most appropriate defaults-x.y.z.css file for any given version.
    Also updated flex-jars eclipse project classpath to reflect recent Batik jar consolidation.
    QE: Yes, please change any negative test cases that were checking for --compatibility-version=3 as this is now valid.
    Doc: No
    Checkintests: Pass
    Reviewer: Paul
    Bugs:
    SDK-21182 - Fix logic surrounding compatibility version and SWC default.css selection during PreLink
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21182
        http://bugs.adobe.com/jira/browse/SDK-21182
    Modified Paths:
        flex/sdk/branches/3.x/development/eclipse/java/flex-jars/.classpath
        flex/sdk/branches/3.x/modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.j ava

  • I downloaded Lion onto my Mac, and now cannot open or access any of my Microsoft word documents or Power Points. Is there a fix for this? I need my documents

    I downloaded Lion onto my Mac, and now cannot open or access any of my Microsoft word documents or Power Points. Is there a fix for this? I need my documents

    If it's because you were using Office 2004, the eight year old version of Office that was written when Intel processors were not used in Macs, then there will be no fix. Lion dropped support for PowerPC applications, as has been widely reported since Lion's release last August.
    You can upgrade Office 2004 to Office 2008 or Office 2011. You can use iWorks 2009 that can open Microsoft files. You can use a number of free applications that are also capable of working with Microsoft documents. You can go back to Snow Leopard, if you have a backup. Or, if you have an external drive or room to add a partition to your current drive, you can install Snow Leopard on it.
    Search these forums for more information. If this is your issue, it's been posted and answered several times a day since August 2011.

  • I plugged in my brand new nano to my husbands desktop to get it registered, but had a problem mid way through when I tried to used an apple login that already existed.  Now it's not registered and the computer won't recognize my device.  How do I fix this

    I plugged in my brand new nano to my husbands desktop to get it registered, but had a problem mid way through when I tried to used an apple login that already existed.  Now it's not registered and the computer won't recognize my device.  How do I fix this?

    iPod not recognized in 'My Computer' and in iTunes for Windows
    Call U.S. iPod and Mac technical support: 1-800-APL-CARE (1-800-275-2273) to register your iPod Nano.

  • [svn:fx-trunk] 11448: Making a small ItemRenderer change so that we don' t dispatch an unused, contentBackgroundColorChanged event anymore when the itemIndex gets set.

    Revision: 11448
    Author:   [email protected]
    Date:     2009-11-04 17:06:22 -0800 (Wed, 04 Nov 2009)
    Log Message:
    Making a small ItemRenderer change so that we don't dispatch an unused, contentBackgroundColorChanged event anymore when the itemIndex gets set.
    QE notes: -
    Doc notes: -
    Bugs: -
    Reviewer: Deepa
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ItemRenderer .as

    Revision: 11448
    Author:   [email protected]
    Date:     2009-11-04 17:06:22 -0800 (Wed, 04 Nov 2009)
    Log Message:
    Making a small ItemRenderer change so that we don't dispatch an unused, contentBackgroundColorChanged event anymore when the itemIndex gets set.
    QE notes: -
    Doc notes: -
    Bugs: -
    Reviewer: Deepa
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ItemRenderer .as

  • [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: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.

Maybe you are looking for