[svn:osmf:] 17980: Fix FM-1092: Calling stop when loop is true breaks looping.

Revision: 17980
Revision: 17980
Author:   [email protected]
Date:     2010-09-30 17:42:23 -0700 (Thu, 30 Sep 2010)
Log Message:
Fix FM-1092: Calling stop when loop is true breaks looping.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1092
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as

Hi Experts,
After i tried a few times, i can successfully start prepare with upgrade asistant monitor - Administrator >> Start Prepare,
Thanks

Similar Messages

[svn:osmf:] 14754: Fix bug FM-555: RTE when SerialElement child has a load error.

Revision: 14754
Revision: 14754
Author:   [email protected]
Date:     2010-03-15 09:25:26 -0700 (Mon, 15 Mar 2010)
Log Message:
Fix bug FM-555: RTE when SerialElement child has a load error.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-555
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/TraitLoader.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/compositeClasses/TestTraitLoader.as

(Removed)

[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

Xcode debugger stops when NOT going through break

I have some c++ code, very simple:
195 MyModelItem *parentItem = thisItem->parent();
196 if(parentItem == NULL)
197 {
198 std::cout << "parentItem is NULL\n";
199 bool parentIsNull = true;
200 if(parentIsNull)
201 return QModelIndex();
202 return QModelIndex();
203 }
204 else if((unsigned int)parentItem == 0x4d0000)
205 {
206 std::cout << "parentItem is 0x4d0000\n";
207 return QModelIndex();
208 }
209 else if (parentItem == m_root)
210 return QModelIndex();
211
212 return createIndex(parentItem->row(), 0, parentItem);
213 }
I put a breakpoint on line 200 -- the one that is inside the if-clause and says:
bool parentIsNull = true;
There is a cout right above that line. So the breakpoint should not be triggered except when parentItem is NULL, and the debugger console should have the "parentItem is NULL" message logged to it.
But, in fact, the breakpoint gets triggered every single solitary time the function gets called. According to the GDB status reported on the debugger console, it claims that it has stopped at "Breakpoint 1" and that it is "Line 200". Line 200 is indeed the line that I put the breakpoint on, but the little red arrow is not on Line 200, it's on Line 204. If I single-step after the breakpoint stops, it goes to line 209, then the red arrow jumps to the "return" statement which is at the end of the previous function in the file, and then finally to line 213 -- which is one line after the actual return statement.
So does anyone know any way to get the debugger to behave? To only stop when the breakpoint in question actually gets triggered? It would be nice if the single-step behavior followed what code is supposed to be executing, but I would settle for not stopping at "phantom" triggers.

When I type "clear" at the gdb prompt, I get a "No source file specified" error...
I'm not sure that I am being clear on my problem here. I have a breakpoint at line 200. Line 200 is inside the if-clause
if(parentItem==NULL) { ... }
I want the program to stop at line 200, but only if parentItem==NULL. In my previous experience with every debugger I've used (including many years using gdb) if you set a break on a line of code that only executes if some condition is true, then the breakpoint only gets triggered, and the program only stops, if the condition is true and the line of code that the breakpoint is on executes. What I am seeing is that Xcode wants to stop at the breakpoint if the line is executed, but also stop at the next line which is executed if that line is not executed. I can set the breakpoint to a log-and-continue state, but then it logs and continues when I want it to stop. I tried setting the condition of parentItem==NULL in the edit breakpoint dialog, but then it says "Error in testing breakpoint condition:"
When I've seen this behavior before it has been related to not getting optimization turned off. (The optimization makes the whole swath of code disappear, and so the debugger just kinds improvises on the line numbers and stops whenever you are in the vicinity.) But I have checked the project settings over and over, and it's set debug, and optimization is set to NONE, and I just can't see anything else to turn on/off to get breakpoints to work.

[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:] 11877: Fix bug FM-194: Calling seek consecutively doesn' t respect the last seek.

Revision: 11877
Revision: 11877
Author:   [email protected]
Date:     2009-11-16 17:21:29 -0800 (Mon, 16 Nov 2009)
Log Message:
Fix bug FM-194: Calling seek consecutively doesn't respect the last seek. The fix is to let each subsequent seek through (previously we blocked a seek attempt if another seek attempt was underway). Update base unit tests. Modify ExamplePlayer's scrub bar to seek while you scrub, this is a good way to demo/test this behavior.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-194
Modified Paths:
    osmf/trunk/apps/samples/framework/ExamplePlayer/org/osmf/view/MainWindow.as
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamSeekableTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/traits/ISeekable.as
    osmf/trunk/framework/MediaFramework/org/osmf/traits/SeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/traits/TestISeekable.as

[svn:osmf:] 14105: Fixed bug where canSeekTo(0) wasn' t checked before the auto rewind code in play was called.

Revision: 14105
Revision: 14105
Author:   [email protected]
Date:     2010-02-10 11:34:06 -0800 (Wed, 10 Feb 2010)
Log Message:
Fixed bug where canSeekTo(0) wasn't checked before the auto rewind code in play was called. Fixed 347.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as

Have I mentioned how much i love my playbook now Great job on os 2.0

[svn:osmf:] 13027: Fix bug in SerialElement where the durationReached event was dispatched on a child-to-child transition due to the base class thinking that the duration had been reached (since the second child didn't have a duration yet).

Revision: 13027
Revision: 13027
Author:   [email protected]
Date:     2009-12-16 18:09:46 -0800 (Wed, 16 Dec 2009)
Log Message:
Fix bug in SerialElement where the durationReached event was dispatched on a child-to-child transition due to the base class thinking that the duration had been reached (since the second child didn't have a duration yet). Injection from trait refactoring.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/CompositeTimeTrait.as

http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/libata/ch07.html#excatATAbusErr wrote:
ATA bus error means that data corruption occurred during transmission over ATA bus (SATA or PATA). This type of errors can be indicated by
ICRC or ABRT error as described in the section called “ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)”.
Controller-specific error completion with error information indicating transmission error.
On some controllers, command timeout. In this case, there may be a mechanism to determine that the timeout is due to transmission error.
Unknown/random errors, timeouts and all sorts of weirdities.
As described above, transmission errors can cause wide variety of symptoms ranging from device ICRC error to random device lockup, and, for many cases, there is no way to tell if an error condition is due to transmission error or not; therefore, it's necessary to employ some kind of heuristic when dealing with errors and timeouts. For example, encountering repetitive ABRT errors for known supported command is likely to indicate ATA bus error.
Once it's determined that ATA bus errors have possibly occurred, lowering ATA bus transmission speed is one of actions which may alleviate the problem.
I'd also add; make sure you have good backups when ATA errors are frequent

[svn:osmf:] 14823: Fix bug where canPause was not set to false for live streams.

Revision: 14823
Revision: 14823
Author:   [email protected]
Date:     2010-03-17 10:51:40 -0700 (Wed, 17 Mar 2010)
Log Message:
Fix bug where canPause was not set to false for live streams.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamPlayTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestVideoElement.as

Thanks for looking at this post. We have resolved the issue for ourselves by working with our DBAs to narrow down where the problem actually started. We found that the particular SQL we were looking at was not the issue. In a chart on a subsequent page (via a click through), we were actually running into where apex was starting to consuming memory but we were catching it later.
What we found was that when we had a chart query that was SQL containing a pipeline function, the memory usage went up. And within 10 minutes, the server would crawl to a halt. To release the memory, the DBAs would have to bounce the Apex instance. When I changed the query to be a function returning SQL, the problem stopped. I don't know what the correlation was between SQL and moving to a PL/SQL function returning SQL.
I am not even 100% positive of the pipeline function being the cause. I only know that this started happening about the same time as when I implemented the pipeline function. I understand you are leery of a one-second function/query running up that kind of utilization. No one here believed me either (including me really). We figured it HAD to be a coincidence. But once I changed the query from SQL to a function returning PL/SQL, our problem went away.
Thanks to all who looked at and thought about this.
Walter

[svn:osmf:] 10248: Fix a few bugs related to the interaction between IPlayable, IPausable, and ITemporal within a SerialElement, specifically around ensuring that the transition from child to child happens in the various permutations of these traits .

Revision: 10248
Author:   [email protected]
Date:     2009-09-14 16:45:00 -0700 (Mon, 14 Sep 2009)
Log Message:
Fix a few bugs related to the interaction between IPlayable, IPausable, and ITemporal within a SerialElement, specifically around ensuring that the transition from child to child happens in the various permutations of these traits. Introduce a helper class for managing this logic, as it can happen in both CompositePlayableTrait and CompositeTemporalTrait. This lays the groundwork for a MediaElement which only implements IPlayable (e.g. to ping a tracking server) working within a serial composition. Beef up unit tests so that these cases don't get broken in the future.
Modified Paths:
    osmf/trunk/framework/MediaFramework/.flexLibProperties
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/composition/CompositePlayableTrai t.as
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/composition/CompositeTemporalTrai t.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/composition/TestSerialEle ment.as
Added Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/composition/SerialElementTransiti onManager.as

Hi,
Found a note explaining the significance of these errors.
It says:
"NZE-28862: SSL connection failed
Cause: This error occurred because the peer closed the connection.
Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
Thanks & Regards,
Sindhiya V.

[svn:osmf:] 17761: Fix FM-1049: OSMFAIRTest compile errors.

Revision: 17761
Revision: 17761
Author:   [email protected]
Date:     2010-09-17 17:05:15 -0700 (Fri, 17 Sep 2010)
Log Message:
Fix FM-1049: OSMFAIRTest compile errors. OSMFAIRTest (& OSMFIntegrationTest) now default to 10.1, and to AIR 2.0. To run this on AIR 1.5, you need to make sure you're using a compatible SDK and a compatible set of FLASH_10_1 flags.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1049
Modified Paths:
    osmf/trunk/framework/OSMFAIRTest/.actionScriptProperties
    osmf/trunk/framework/OSMFAIRTest/OSMFAIRTest-app.xml
    osmf/trunk/framework/OSMFIntegrationTest/.actionScriptProperties

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.

[svn:osmf:] 16167: Fix FM-863: RTE when scrubbing to the end of the child of a SerialElement when that SerialElement has a ParallelElement within it .

Revision: 16167
Revision: 16167
Author:   [email protected]
Date:     2010-05-17 16:47:05 -0700 (Mon, 17 May 2010)
Log Message:
Fix FM-863: RTE when scrubbing to the end of the child of a SerialElement when that SerialElement has a ParallelElement within it.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-863
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/CompositeTimeTrait.as

When I see code errors, I stop trying to trouble shoot because code errors account for 98% of browser rendering problems. When you clear up your orphaned tags: mismatched <p></p> and <li></li> tags, then I'll take a closer look.
PS. Being able to work with code is essential to using DW and 3rd party plugins. Without basic coding skills, you're going to be lost most of the time.
HTML & CSS Tutorials -
http://www.html.net/
http://w3schools.com/
Nancy O.

[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:] 14067: Fixed a bug in DynamicStreamingSample that Ivonne found.

Revision: 14067
Revision: 14067
Author:   [email protected]
Date:     2010-02-09 11:09:35 -0800 (Tue, 09 Feb 2010)
Log Message:
Fixed a bug in DynamicStreamingSample that Ivonne found.
Modified Paths:
    osmf/trunk/apps/samples/framework/DynamicStreamingSample/src/DynamicStreamingSample.mxml

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: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:] 17980: Fix FM-1092: Calling stop when loop is true breaks looping.

Similar Messages

Maybe you are looking for