[svn:osmf:] 11142: Fixing even listener being added to loader instead of contentLoaderInfo.

Revision: 11142
Author:   [email protected]
Date:     2009-10-26 04:08:48 -0700 (Mon, 26 Oct 2009)
Log Message:
Fixing even listener being added to loader instead of contentLoaderInfo.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/content/ContentDownloadableTrait.as

I solved this problem.

Similar Messages

[svn:osmf:] 15000: Fix for FM-447 : Adding CuePoint in TemporalFacet event listeners doesn't work

Revision: 15000
Revision: 15000
Author:   [email protected]
Date:     2010-03-24 14:01:02 -0700 (Wed, 24 Mar 2010)
Log Message:
Fix for FM-447 : Adding CuePoint in TemporalFacet event listeners doesn't work
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-447
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/metadata/TimelineMetadata.as

[svn:osmf:] 14975: Fix for FM-447 : Adding CuePoint in TemporalFacet event listeners doesn't work

Revision: 14975
Revision: 14975
Author:   [email protected]
Date:     2010-03-23 17:04:43 -0700 (Tue, 23 Mar 2010)
Log Message:
Fix for FM-447 : Adding CuePoint in TemporalFacet event listeners doesn't work
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-447
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/metadata/TimelineMetadata.as

[svn:osmf:] 10707: Fixing FM-113 by adding a null check.

Revision: 10707
Author:   [email protected]
Date:     2009-09-29 18:26:03 -0700 (Tue, 29 Sep 2009)
Log Message:
Fixing FM-113 by adding a null check.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-113
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/composition/ParallelSeekableTrait .as

First, if this is your only backup, you must make another full backup to a locally-attached external hard drive. One backup is never enough to be safe, and backing up over a network is less reliable than backing up locally.
Hold down the option key and select Verify Backups from the Time Machine menu in the menu bar (not the Dock icon.) This operation may take several hours. If the menu-bar icon (a clock that runs backwards) isn't showing, check Show Time Machine in menu bar in the Time Machine preference pane.

[svn:osmf:] 14812: Fix bug where setting a resource a second time on a VideoElement caused an RTE due to the loadStateChange event listener being unregistered too soon .

Revision: 14812
Revision: 14812
Author:   [email protected]
Date:     2010-03-17 09:02:11 -0700 (Wed, 17 Mar 2010)
Log Message:
Fix bug where setting a resource a second time on a VideoElement caused an RTE due to the loadStateChange event listener being unregistered too soon.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/LoadableElementBase.as

Revision: 14812
Revision: 14812
Author:   [email protected]
Date:     2010-03-17 09:02:11 -0700 (Wed, 17 Mar 2010)
Log Message:
Fix bug where setting a resource a second time on a VideoElement caused an RTE due to the loadStateChange event listener being unregistered too soon.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/LoadableElementBase.as

[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:] 14598: Fix FM-500: reinstating onMetaData handler clause that prevents incoming dimensions from being applied if they are not different from the dimensions that were already set .

Revision: 14598
Revision: 14598
Author:   [email protected]
Date:     2010-03-05 02:13:40 -0800 (Fri, 05 Mar 2010)
Log Message:
Fix FM-500: reinstating onMetaData handler clause that prevents incoming dimensions from being applied if they are not different from the dimensions that were already set.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-500
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamDisplayObjectTrait.as

You are welcome. I'm glad you got it back up.
(1) You say you did the symbolic link. I will assume this is set correctly; it's very important that it is.
(2) I don't know what you mean by "Been feeding the [email protected] for several weeks now, 700 emails each day at least." After the initial training period, SpamAssassin doesn't learn from mail it has already processed correctly. At this point, you only need to teach SpamAssassin when it is wrong. [email protected] should only be getting spam that is being passed as clean. Likewise, [email protected] should only be getting legitimate mail that is being flagged as junk. You are redirecting mail to both [email protected] and [email protected] ... right? SpamAssassin needs both.
(3) Next, as I said before, you need to implement those "Frontline spam defense for Mac OS X Server." Once you have that done and issue "postfix reload" you can look at your SMTP log in Server Admin and watch as Postfix blocks one piece of junk mail after another. It's kind of cool.
(4) Add some SARE rules:
Visit http://www.rulesemporium.com/rules.htm and download the following rules:
70sareadult.cf
70saregenlsubj0.cf
70sareheader0.cf
70sarehtml0.cf
70sareobfu0.cf
70sareoem.cf
70sarespoof.cf
70sarestocks.cf
70sareunsub.cf
72sare_redirectpost
Visit http://www.rulesemporium.com/other-rules.htm and download the following rules:
backhair.cf
bogus-virus-warnings.cf
chickenpox.cf
weeds.cf
Copy these rules to /etc/mail/spamassassin/
Then stop and restart mail services.
There are other things you can do, and you'll find differing opinions about such things. In general, I think implementing the "Frontline spam defense for Mac OS X Server" and adding the SARE rules will help a lot. Good luck!

[svn:osmf:] 11359: Fixing MetadataWatcher not invoking a value change callback when the parent facet of the target value is added or removed .

Revision: 11359
Author:   [email protected]
Date:     2009-11-02 05:20:01 -0800 (Mon, 02 Nov 2009)
Log Message:
Fixing MetadataWatcher not invoking a value change callback when the parent facet of the target value is added or removed.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/MetadataWatcher.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestMetadataUtils.as

mikeporter wrote:
I'm sorry I'm not aware of any "cumbersome" subpanels - unless of course you don't know what you're doing. There is this wonderful invention called a "subVI" that can be used to organize and simplify your code, or are they too "cumbersome" as well? You should really learn a bit about what you are pontificating over before you start running off at the mouth.
Mike...
I didn't want to step on your toes. No need to get personal.
Subpanels make some additional code necessary that hasn't got to do anything with the actual program. And I AM using subIVs as I wrote in my first post, which is exactly the root of the problem.
Nevertheless I now solved it in a way that comes close to what I wanted. I don't know if some of you meant your suggestions to be understood that way (at least I didn't ). The subVIs will now "insert" themselves (via invoke node) into a subpanel on the main vi, which they are given a reference of at call. This adds minimal aditional code, especially on the main VI which I want to keep as clean as possible. By clustering the panel reference into the parameters the subVIs are already given (not used in the example I attached below), there isn't even a change on the terminals of the subVIs.
I got to check now if this works well with event structures within the subVIs or if it can create the same problems like multiple event structures within a single VI.
So no global variables anymore and no writing values by property node. I don't know if this just wasn't possible in previous Labview versions I had a try at that (I guess it was 8.6 and/or 2009) or I just didn't come up with the idea back then.
And if the text wasn't that helpful, here are two screens:
Parent VI:
SubVI:
Attachments:
main.png ‏2 KB
subvi.png ‏5 KB

[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:] 14928: Fix bug FM-468: Initial and max indices not being respected for RTMP MBR.

Revision: 14928
Revision: 14928
Author:   [email protected]
Date:     2010-03-22 17:35:43 -0700 (Mon, 22 Mar 2010)
Log Message:
Fix bug FM-468: Initial and max indices not being respected for RTMP MBR.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-468
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamSwitchManager.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/TestNetStreamSwitchManager.as

[svn:osmf:] 9861: Fixing bug where sizing pixel from the previous run of updateIntrinsicDimensions would prevent the dimensions from being decreased .

Revision: 9861
Author:   [email protected]
Date:     2009-08-31 23:08:03 -0700 (Mon, 31 Aug 2009)
Log Message:
Fixing bug where sizing pixel from the previous run of updateIntrinsicDimensions would prevent the dimensions from being decreased.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/layout/LayoutContextSprite.as

[svn:osmf:] 13557: Fixing problem where a lingering TraitAggregationHelper causes elements to be added multiple times on ParallelDisplayObjectTrait .

Revision: 13557
Revision: 13557
Author:   [email protected]
Date:     2010-01-17 10:05:12 -0800 (Sun, 17 Jan 2010)
Log Message:
Fixing problem where a lingering TraitAggregationHelper causes elements to be added multiple times on ParallelDisplayObjectTrait.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/ParallelDisplayObjectTrait.as

Revision: 13557
Revision: 13557
Author:   [email protected]
Date:     2010-01-17 10:05:12 -0800 (Sun, 17 Jan 2010)
Log Message:
Fixing problem where a lingering TraitAggregationHelper causes elements to be added multiple times on ParallelDisplayObjectTrait.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/ParallelDisplayObjectTrait.as

[svn:osmf:] 14982: Fixing some event parameters not being forwarded.

Revision: 14982
Revision: 14982
Author:   [email protected]
Date:     2010-03-24 02:15:50 -0700 (Wed, 24 Mar 2010)
Log Message:
Fixing some event parameters not being forwarded.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/DebuggerElementProxy.as

Hi,
Thanks for posting in Microsoft TechNet forums.
I will try to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Kate Li
TechNet Community Support

[svn:osmf:] 13558: Fixing element removal failure due to ParallelDisplayObject trait not being able to resolve media element from view trait .

Revision: 13558
Revision: 13558
Author:   [email protected]
Date:     2010-01-17 10:18:44 -0800 (Sun, 17 Jan 2010)
Log Message:
Fixing element removal failure due to ParallelDisplayObject trait not being able to resolve media element from view trait. Extended TraitAggregatorEvent to include to media element so resolving is no longer required.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/ParallelDisplayObjectTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/TraitAggregationHelper.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/TraitAggregator.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/TraitAggregatorEvent.as

[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:] 11142: Fixing even listener being added to loader instead of contentLoaderInfo.

Similar Messages

Maybe you are looking for