Revision: 12387
Revision: 12387
Author: rfrishbe@adobe.com
Date: 2009-12-02 12:38:05 -0800 (Wed, 02 Dec 2009)
Log Message:
***********
VideoDisplay/VideoPlayer changes. The two big changes are making sure we don?\226?\128?\153t call any methods on the media player when the state is ?\226?\128?\156loading?\226?\128?\157 or ?\226?\128?\156uninitialized?\226?\128?\157. Before we were just checking for ?\226?\128?\156playbackError?\226?\128?\157; however, at the time of these other states, it?\226?\128?\153s not valid to call methods on mediaPlayer either. Also, I alphabetized and organized the methods and properties in VolumeBar and also fixed a bug where we were setting muted = false in setValue(). We did this so that when the user moves around the track or the thumb, muted gets unset, but we should only do this on changes due to a user-interaction. So I?\226?\128?\153ve moved this code to a CHANGE handler instead. All the other changes should be relatively minor.
QE notes: -
Doc notes: -
Bugs: SDK-24192, SDK-24486
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
***********
http://bugs.adobe.com/jira/browse/SDK-24192
http://bugs.adobe.com/jira/browse/SDK-24486
Modified Paths:
**************
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoDisplay.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/mediaClasses/MuteButton.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/components/mediaClasses/VolumeBar.as