Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This event occurs when the ready state changes.

Compatibility:Windows Media Player, ActiveMovie

Syntax

<SCRIPT FOR="MediaPlayer" EVENT="ReadyStateChange(
lReadyState)" LANGUAGE="JScript">
  //insert script commands//
</SCRIPT>

Parameters

lReadyState

Longvalue indicating the current value of the ReadyState property, after it changes.

Remarks

The following are possible values for the lReadyStateparameter.

Value Visual Basic constant Description

0

mpReadyStateUninitialized

The FileNameproperty has not been initialized.

1

MpReadyStateLoading

The Windows Media Player control is asynchronously loading a file.

3

MpReadyStateInteractive

The Windows Media Player control loaded a file, and downloaded enough data to play the file, but has not yet received all data.

4

MpReadyStateComplete

All data has been downloaded.

After calling the Openmethod, applications should check the ready state before attempting to call the Playmethod on the newly opened file.

Applications should call the Playmethod only if the lReadyStateparameter equals 3 ( mpReadyStateInteractive) or 4 ( mpReadyStateComplete).

ActiveMovie compatibility mode is only supported through Windows CE .NET 4.1.

Requirements

Windows Embedded CE Windows CE 3.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.