Embedding a presentation in a Web page lets you play back clips without launching RealPlayer as a separate application. You can even include in your page RealPlayer controls for actions such as fast-forward and pause. This chapter explains how you add markup to a Web page so that people view your RealSystem presentation directly through their Web browsers.
![]() |
Additional Information |
---|
For a quick example of how to embed a video in a Web page, see "Embedding a RealVideo Clip in a Web Page". |
To provide Web page playback, RealPlayer includes a plug-in for browsers that support the Netscape plug-in architecture:
RealPlayer also has an ActiveX control that provides playback capabilities within the following products:
Because they both have the same capabilities, you can use either the plug-in or the ActiveX control, depending on which products you need to support. The following sections describe the basics of using the plug-in or the control and explain each parameter you can set.
![]() |
Additional Information |
---|
Embedded RealPlayer Extended Functionality Guide at http://service.real.com/help/library/encoders.html explains how to use JavaScript or VBScript to extend the functionality of the Netscape plug-in or the ActiveX control. |
To use RealPlayer's Netscape plug-in, you add <EMBED>
tags to your Web page HTML. Each <EMBED>
tag has three required parameters (SRC
, WIDTH
, HEIGHT
) and can include many optional parameters. The basic <EMBED>
tag looks like the following (the SRC
value, which is explained below, has been omitted for simplicity):
<EMBED SRC="..." WIDTH=300 HEIGHT=134>
This tag creates a playback area 300 pixels wide by 134 pixels high within the Web page. Parameters are typically in the form PARAMETER=value
. Parameter names can be any case, although this manual shows them uppercase. Except for file names, which typically must be lowercase, parameter values are not case-sensitive. Unless they are URLs, parameter values do not need to be enclosed in quotation marks.
To accommodate browsers that do not support the Netscape plug-in, use <NOEMBED>
to define a standard hypertext link to your presentation. The unembedded link follows the <EMBED>
tag:
<EMBED SRC="..." WIDTH=300 HEIGHT=134>
<NOEMBED><A HREF="...">Play with RealPlayer.</A></NOEMBED>
In this example, browsers that can play the embedded presentation hide the text between <NOEMBED>
and </NOEMBED>
. Other browsers ignore the preceding <EMBED>
tag and display only the hypertext link. The user then clicks the link to play the presentation in RealPlayer.
You embed the RealPlayer ActiveX control in HTML pages by using the <OBJECT>
tag. This tag uses an ID that you select, such as ID=RVOCX
, and it must have the following class ID, which identifies RealPlayer:
CLASSID="clsid:CFCDAA03-8BE4-11cf-B84B-0020AFBBCCFA"
The <OBJECT>
tag also sets the width and height of the playback area within the browser. A typical <OBJECT>
tag looks like this:
<OBJECT ID=RVOCX CLASSID="clsid:CFCDAA03-8BE4-11cf-B84B-0020AFBBCCFA"
WIDTH=300 HEIGHT=134>
... parameters ...
</OBJECT>
This tag creates a playback area 300 pixels wide by 134 pixels high within the Web page. Between <OBJECT>
and </OBJECT>
, you can define any number of additional parameters with the following syntax:
<PARAM NAME="name
" VALUE="value
">
PARAM
, NAME
, and VALUE
markers can be any case, although in this book they are uppercase. Parameter values are not case-sensitive, except for file names, which typically must be lowercase. Always enclose parameter values in double quotation marks.
Both the Netscape plug-in and the ActiveX control use the same basic tag parameters. As explained in the preceding section, however, the tag syntaxes for the plug-in and the control differ. This section explains the basic parameters you can include in each <EMBED>
or <OBJECT>
tag.
The SRC
parameter gives the presentation's source URL enclosed in double quotation marks. The directory names cannot contain spaces. For the ActiveX control, the <OBJECT>
tag's CLASSID
parameter causes the presentation to play in the Web page, so you can simply link to the SMIL file or clip within one <OBJECT>
tag. When linking to a presentation on RealServer, you can include the Ramgen parameter in the URL, as in the following example (although this is not necessary):
<PARAM NAME="SRC" VALUE="http://realserver.example.com:8080/ramgen/sample.smil">
When you use the Netscape plug-in, you need to include the SRC parameter in every <EMBED>
tag. You can specify two types of URLs. The first uses the ?embed
option of the Ramgen parameter, which causes RealPlayer to play the clip or SMIL presentation through its Netscape plug-in instead of launching as a separate application:
SRC="http://realserver.example.com:8080/ramgen/sample.smil?embed"
![]() |
Additional Information |
---|
For more on Ramgen and presentation URLs, see "Linking Your Web Page to RealServer". |
The second option is to create a Ram file with a .rpm extension and list this file in the SRC
parameter without including Ramgen and the ?embed
option. The Ram file then links to your SMIL file or clips. The following example links to a .rpm
file on a Web server:
SRC="http://www.example.com/media/sample.rpm"
![]() |
Additional Information |
---|
For instructions on writing a .rpm file, see "Creating a Ram File Manually". |
You must create and link to a .rpm
file in any of the following situations:
Required for each <EMBED>
or <OBJECT>
tag, the WIDTH
and HEIGHT
parameters set the size of the playback area. If you omit these parameters, the playback area may appear as a tiny icon because streaming media presentations do not resize themselves automatically. The values for WIDTH
and HEIGHT
are in pixels by default, so a width of 300 creates a playback area 300 pixels wide. Setting WIDTH
and HEIGHT
to 0 (zero) hides the playback area.
You can also express WIDTH
and HEIGHT
as percentages of the browser window size. For example, a width of 50% makes the width of the presentation area half the width of the browser window. Keep in mind that different types of media scale with different results. For example, a video scaled larger than its encoded size may not look good. Vector-based clips such as Flash animations, on the other hand, scale more easily to fit different playback areas.
Setting the NOJAVA
parameter to true
in every <EMBED>
tag prevents the browser's Java Virtual Machine (JVM) from starting if it is not yet running:
<EMBED SRC="..." WIDTH=300 HEIGHT=134 NOJAVA=true>
This is recommended when using the Netscape plug-in because the JVM is not required for the <EMBED>
parameters described in this chapter. Starting the JVM therefore delays presentation playback unnecessarily. The JVM is required only when you are extending plug-in functionality with JavaScript. In this case, omit NOJAVA
entirely from the <EMBED>
tags.
![]() |
Additional Information |
---|
See Embedded RealPlayer Extended Functionality Guide at http://service.real.com/help/library/index.html for more information on controlling RealPlayer with JavaScript. |
![]() |
Note |
---|
Although you can include NOJAVA as an ActiveX
parameter, it has no effect on Internet Explorer, which
starts its JVM when the browser is launched.
|
With the CONTROLS
parameter, you can add RealPlayer controls such as a play/pause button to your Web page. Visitors to your page can then control the presentation playback as if they were using RealPlayer as a separate application. The following example for the Netscape <EMBED>
tag displays the play/pause button in your Web page:
<EMBED SRC="..." WIDTH=26 HEIGHT=26 NOJAVA=true CONTROLS=PlayButton
>
For the ActiveX control, you define a CONTROLS
parameter within the <OBJECT>
tag structure:
<OBJECT ID=RVOCX CLASSID="..." WIDTH=26 HEIGHT=26>
<PARAM NAME="SRC" VALUE="..."><PARAM NAME="CONTROLS" VALUE="PlayButton">
</OBJECT>
The following sections describe the embedded RealPlayer controls. You use a tag's WIDTH
and HEIGHT
parameters to set the control's size. The suggested pixel widths and heights given with the control descriptions produce controls approximately the same sizes as the RealPlayer controls. Specifying different pixel sizes scales the controls larger or smaller. You can also use percentage values for sizes, but this is recommended only for the image window.
![]() |
Additional Information |
---|
For information on adding more than one control to your Web page, see "Linking Multiple Controls". |
![]() |
Tip |
---|
If you have RealPlayer installed and are viewing this document from your local computer rather than over the Internet, you can view all the embedded controls. |
Displays the image window. This is available only for display presentations such as video or animation. Even if no other controls are visible on the page, the user can typically right-click (on Windows) or hold down the mouse button (on the Macintosh) in the playback area to display a menu of choices such as Play and Stop. See also "Controlling Image Display".
Suggested pixel width: | 176 or greater |
Suggested pixel height: | 132 or greater |
Displays the basic RealPlayer control panel. The control name "default" also works. Functions include play, pause, stop, fast-forward, and rewind. Sliders include a position slider and a volume slider with a mute button that pops up when the speaker button is clicked. Below the buttons are a clip information field, a status panel, a network congestion indicator, and a clip timing field.
Suggested pixel width: | 375 |
Suggested pixel height: | 100 |
Displays a compact RealPlayer control panel. Functions include play, pause, stop, fast-forward and rewind. There's also a position slider, along with a volume slider and mute button that pops up when the speaker button is clicked.
Suggested pixel width: | 350 |
Suggested pixel height: | 36 |
Suggested pixel width: | 44 |
Suggested pixel height: | 26 |
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Displays a fast-forward button.
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Suggested pixel width: | 26 |
Suggested pixel height: | 26 |
Displays a mute button and volume slider.
Suggested pixel width: | 26 |
Suggested pixel height: | 88 |
Suggested pixel width: | 26 |
Suggested pixel height: | 65 |
Displays a clip position slider.
Suggested pixel width: | 120 |
Suggested pixel height: | 26 |
Displays a clip information field. For instructions on formatting the clip playlist, see "Managing the Playlist".
Suggested pixel width: | 370 |
Suggested pixel height: | 32 |
Suggested pixel width: | 45 |
Suggested pixel height: | 25 |
Displays presentation information along with the volume slider and mute button. For more on presentation information, see "Adding Presentation Information". See also "NOLABELS".
Suggested pixel width: | 325 |
Suggested pixel height: | 55 |
Displays the presentation information panel. For more on presentation information, see "Adding Presentation Information". See also "NOLABELS".
Suggested pixel width: | 300 |
Suggested pixel height: | 55 |
Displays the status panel, which shows informational messages. It also includes the network congestion LED and the position field, which shows the clip's current place in the presentation timeline along with the total clip length.
Suggested pixel width: | 300 |
Suggested pixel height: | 30 |
![]() |
Note |
---|
The status bar is included in the All control. If you do
not embed a status bar or status field in your page, error
messages display in the browser's status bar.
|
Displays the message text area of the status bar. If you do not embed a status field or status bar in your page, error messages display in the browser's status bar.
Suggested pixel width: | 200 |
Suggested pixel height: | 30 |
Displays the position field, which shows the clip's current place in the presentation timeline and the total clip length.
Suggested pixel width: | 90 |
Suggested pixel height: | 30 |
The CONSOLE
parameter defines a name that unifies <EMBED>
or <OBJECT>
tags so that multiple controls work together. For example, you could create three separate <EMBED>
or <OBJECT>
tags to define an image window, a play button, and a stop button. By using three tags, you can set the size of each control separately and define its layout with HTML tags. For example, you could put each control in a different HTML table cell.
To tie controls together, define the same CONSOLE
name within each <EMBED>
or <OBJECT>
tag, or use one of these predefined names:
_master
links the control to all other embedded controls on the page.
_unique
links the control to no other embedded controls on the page.
You can have multiple console names for separate presentations. For a page showing two video clips, for example, you can define the console names video1
and video2
. All controls linked by video1
interoperate, as do all controls linked by video2
. But a video1
volume slider, for example, will not affect the volume of a video2
clip.
Note the following when grouping multiple controls with CONSOLE
attributes:
<EMBED>
tag must have a SRC
attribute. Tags linked by a console name should have the same SRC
value.
<OBJECT>
tag in a console group needs to have a SRC
value.
<EMBED>
or <OBJECT>
tags in a console group have different SRC
values, the first valid source that RealPlayer finds among those choices becomes the console source. This may not always be the first source listed.
The following examples for the <EMBED>
and <OBJECT>
tags set up an image window and two sets of controls (a play button and stop button) for two separate videos, sample1.rm and sample2.rm. The predefined console name _master
links the image window to both control sets. The control sets use different console names, however, so they do not link to each other. Clicking each play button therefore starts a different video.
Because each <EMBED>
tag must have a SRC
value, the image window in the following example uses the same source as the first play button. The viewer simply clicks either play button to start a video. Clicking the other play button stops the first video and plays the second one:
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample1.rm?embed"
WIDTH=176 HEIGHT=128 NOJAVA=true CONTROLS=ImageWindowCONSOLE=_master
>
<H4>Video 1</H4>
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample1.rm?embed"
WIDTH=44 HEIGHT=26 NOJAVA=true CONTROLS=PlayButtonCONSOLE=video1
>
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample1.rm?embed"
WIDTH=26 HEIGHT=26 NOJAVA=true CONTROLS=StopButtonCONSOLE=video1
>
<H4>Video 2</H4>
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample2.rm?embed"
WIDTH=44 HEIGHT=26 NOJAVA=true CONTROLS=PlayButtonCONSOLE=video2
>
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample2.rm?embed"
WIDTH=26 HEIGHT=26 NOJAVA=true CONTROLS=StopButtonCONSOLE=video2
>
In the following ActiveX example, only the controls for the two play buttons define the source URLs (for convenience the CLASSID
value is omitted):
<OBJECT ID=RVOCX CLASSID="..." WIDTH=176 HEIGHT=128>
<PARAM NAME="CONTROLS" VALUE="ImageWindow"><PARAM NAME="CONSOLE" VALUE="_master">
</OBJECT>
<H4>Video 1</H4>
<OBJECT ID=RVOCX CLASSID="..." WIDTH=44 HEIGHT=26>
<PARAM NAME="SRC" VALUE="http://realserver.example.com:8080/ramgen/sample1.rm">
<PARAM NAME="CONTROLS" VALUE="PlayButton"><PARAM NAME="CONSOLE" VALUE="video1">
</OBJECT>
<OBJECT ID=RVOCX CLASSID="..." WIDTH=26 HEIGHT=26>
<PARAM NAME="CONTROLS" VALUE="StopButton"><PARAM NAME="CONSOLE" VALUE="video1">
</OBJECT>
<H4>Video 2</H4>
<OBJECT ID=RVOCX CLASSID="..." WIDTH=44 HEIGHT=26>
<PARAM NAME="SRC" VALUE="http://realserver.example.com:8080/ramgen/sample2.rm">
<PARAM NAME="CONTROLS" VALUE="PlayButton"><PARAM NAME="CONSOLE" VALUE="video2">
</OBJECT>
<OBJECT ID=RVOCX CLASSID="..." WIDTH=26 HEIGHT=26>
<PARAM NAME="CONTROLS" VALUE="StopButton"><PARAM NAME="CONSOLE" VALUE="video2">
</OBJECT>
The following <EMBED>
and <OBJECT>
parameters control aspects of how clips play back. This example shows two of these parameters used with the Netscape plug-in:
<EMBED SRC="..." WIDTH=50% HEIGHT=50% NOJAVA=true BACKGROUNDCOLOR=gray CENTER=true
>
This example is for the ActiveX control:
<OBJECT ID=RVOCX CLASSID="..." WIDTH=50% HEIGHT=50%>
<PARAM NAME="SRC" VALUE="..."><PARAM NAME="BACKGROUNDCOLOR" VALUE="gray">
</OBJECT>
<PARAM NAME="CENTER" VALUE="true">
This parameter specifies a background color for the image window. The specified background color also shows through if a clip includes transparency. The background color is black by default. You can use an RGB hexadecimal color value (#RRGGBB) or the following color names, shown here with their corresponding RGB values:
![]() |
Note |
---|
SMIL region background colors override this background color. For more on setting SMIL region colors, see "Adding Background Colors". |
The default value for CENTER
is false, which causes the clip to fill the entire playback area. If you set CENTER
to true, the clip is centered within the playback area and is displayed at its encoded size. So by setting CENTER
to true, you can create a large playback area with WIDTH
and HEIGHT
and still have the clip play at its normal size. You cannot use CENTER
along with MAINTAINASPECT
.
This parameter, which you cannot combine with CENTER
, determines whether the clip's height-to-width ratio stays constant when the clip scales to fit the image window. The default value of false causes this ratio to change as necessary to fill the image window fully. This may distort the source image.
If you set MAINTAINASPECT
to true, a clip's height-to-width ratio stays constant. For example, a clip's height-to-width ratio of 1:1 stays constant even if the image window's height-to-width ratio is 2:3. In these cases, the clip is centered in the image window and scaled until one dimension reaches the window's boundaries and the other dimension is within the boundaries. The following illustration shows how clips scale by default, with MAINTAINASPECT
set to true, and with CENTER
set to true.
When you use a control that includes presentation information such as title, author, and copyright, you can include the NOLABELS
option to suppress that information in RealPlayer 5. This option does not affect RealPlayer G2 or later.
![]() |
Additional Information |
---|
The "Parameter Reference" section lists the options that work with RealPlayer 5. |
When set to true, NOLOGO
prevents the Real logo from displaying in the image window. When there are no clips playing, only the specified background color shows in the window. The parameter is false by default.
The AUTOSTART
, LOOP
, and NUMLOOP
parameters let you set a presentation to start playing automatically and to loop continuously or for a specified number of times. The following example shows two of these parameters used with the Netscape plug-in:
<EMBED SRC="..." WIDTH=50% HEIGHT=50% NOJAVA=true AUTOSTART=true LOOP=true
>
This example is for the ActiveX control:
<OBJECT ID=RVOCX CLASSID="..." WIDTH=50% HEIGHT=50%>
<PARAM NAME="SRC" VALUE="..."><PARAM NAME="AUTOSTART" VALUE="true">
</OBJECT>
<PARAM NAME="LOOP" VALUE="true">
When set to true, the AUTOSTART
parameter starts playback immediately. When you have multiple <EMBED>
or <OBJECT>
tags linked by a CONSOLE
name, set AUTOSTART
to true in just one tag. Leaving AUTOSTART
out or setting its value to false means that the presentation will not start until the user starts it by clicking an embedded play button, for example.
If the LOOP
parameter is set to true, the presentation continuously loops until the viewer stops it. When you have multiple <EMBED>
or <OBJECT>
tags linked by a CONSOLE
name, set looping in just one tag. If you leave the LOOP
parameter out, the default value of false applies and the presentation stops after the first playback. The user can play the presentation again by clicking the play button.
If you specify a NUMLOOP
value such as "2"
, the presentation loops the specified number of times and then stops. If you use both LOOP
and NUMLOOP
, the LOOP
parameter is ignored.
The SHUFFLE
parameter is for use only with Ram or SMIL files that list a single sequence of clips. When set to true, SHUFFLE
causes RealPlayer to play back the clips in a random order.
As explained in "Laying Out Multiple Clips", you can use a SMIL file to define separate playback regions for different parts of a presentation. This lets you lay out two clips side-by-side, for example. When playing a presentation in a Web page, you can define the layout in SMIL or in HTML.
To control the layout by using SMIL, you set up the regions and their relative placements in the SMIL file. You then use the Netscape plug-in or the ActiveX control to create a Web page playback area large enough to accommodate all SMIL regions. This SMIL file then produces the same layout when played through the Web page or RealPlayer.
The sample layout shown in "SMIL Layout Example" defines three regions, creating a total playback area 430 pixels wide by 165 pixels high. To accommodate this in your Web page, you define an image window at least as large as this by using either the <EMBED>
or the <OBJECT>
tag. The following example is for the Netscape plug-in:
<EMBED SRC="..." WIDTH=430 HEIGHT=165
NOJAVA=true CONTROLS=ImageWindow CONSOLE=one>
The next example is for the ActiveX control:
<OBJECT ID=RVOCX CLASSID="..."WIDTH=430 HEIGHT=165
>
<PARAM NAME="SRC" VALUE="...">
<PARAM NAME="CONTROLS" VALUE="ImageWindow">
<PARAM NAME="CONSOLE" VALUE="one">
</OBJECT>
The SRC
parameter provides the URL to the SMIL file. You can then use additional <EMBED>
or <OBJECT>
tags linked to the console named "one" to provide RealPlayer controls for the presentation.
![]() |
Additional Information |
---|
If you have installed RealPlayer, click here to see a demonstration with a SMIL layout embedded in a Web page. Click here to see the same demonstration play in RealPlayer. |
The second method omits SMIL layout information and instead defines the layout by using HTML. You could place an image window and separate RealPlayer controls in an HTML table, for example. Each <EMBED>
or <OBJECT>
tag then uses a REGION
parameter to define a region name. The region each clip plays in is denoted by each clip's source tag within the SMIL file. For example, the SMIL file shown in "SMIL Layout Example" lists the following RealText file, which is set to play in the newsregion
region:
<textstream src="news.rt" region="newsregion"/>
Within the HTML page, the <EMBED>
tag that plays news.rt would look like this:
<EMBED SRC="http://realserver.example.com:8080/ramgen/sample.smil?embed"
WIDTH=250 HEIGHT=144 NOJAVA=true CONTROLS=ImageWindowREGION=newsregion
CONSOLE=one>
The <OBJECT>
tag would look like this:
<OBJECT ID=RVOCX CLASSID="..." WIDTH=250 HEIGHT=144>
<PARAM NAME="SRC" VALUE="http://realserver.example.com:8080/ramgen/sample.smil">
<PARAM NAME="CONTROLS" VALUE="ImageWindow"><PARAM NAME="REGION" VALUE="newsregion">
<PARAM NAME="CONSOLE" VALUE="one">
</OBJECT>
You define similar <EMBED>
or <OBJECT>
tags to create other regions for other clips listed in the SMIL file. The SRC
parameter in each tag lists the same SMIL file. You can also use additional <EMBED>
or <OBJECT>
tags linked to the same console to provide RealPlayer controls for the presentation.
![]() |
Additional Information |
---|
If you have installed RealPlayer, click to see a SMIL demonstration embedded in a Web page with an HTML layout. |
When you define the presentation layout through HTML, you must omit the <layout>
section from the SMIL file header. For example, the SMIL file shown in "SMIL Layout Example" would not have a <layout>
section:
<smil>
<head>
<!--presentation with 2 text clips and 1 video clip-->
<meta name="title" content="Music of the Week"/>
</head>
<body>
<par>
<!-- play these 3 clips simultaneously -->
<textstream src="news.rt"region="newsregion"
/>
<video src="newsvid.rm"region="videoregion"
/>
<textstream src="stocks.rt"region="stockregion"
/>
</par>
</body>
</smil>
![]() |
Note |
---|
Because there is no SMIL layout, hot spot links are
ignored. Note, however, that you can make media clips
hyperlinks by using the SMIL <a>...</a> tags. For more
on SMIL hyperlinks, see "Linking to Other Media".
|
The following table lists the <EMBED>
and <OBJECT>
tag parameters. Parameters compatible with RealPlayer 5 are indicated in the "5?" column. To have an embedded presentation play back with RealPlayer 5 as well as RealPlayer G2 or later, use only RealPlayer 5-compatible parameters. Also be sure to use pnm://
instead of rtsp://
in the URL.
Parameter | Function | 5? | Values | Default | |
---|---|---|---|---|---|
AUTOSTART |
Sets automatic playback. | yes | true|false |
false |
|
BACKGROUNDCOLOR |
Sets background color. | no | Color name or RGB hex value | black |
|
CENTER |
Centers clip in the window. | no | true|false |
false |
|
CONSOLE |
Links multiple controls. | yes | Name, _master , or _unique |
(none) | |
CONTROLS |
Adds RealPlayer controls. | yes | Control name | All |
|
HEIGHT |
Sets window or control height. | yes | Percentage or pixels | (none) | |
LOOP |
Loops clips indefinitely. | no | true|false |
false |
|
MAINTAINASPECT |
Preserves image aspect ratio. | no | true|false |
false |
|
NOJAVA |
Prevents JVM start-up. | no | true|false |
false |
|
NOLABELS |
Suppresses presentation information in RealPlayer 5.0. | yes | true|false |
false |
|
NOLOGO |
Suppresses RealLogo. | no | true|false |
false |
|
NUMLOOP |
Loops clip a given number of times. | no | Any number | (none) | |
REGION |
Ties clip to SMIL region. | no | SMIL region | (none) | |
SHUFFLE |
Randomizes playback. | no | true|false |
false |
|
SRC |
Specifies source clip. | yes | URL | (none) | |
WIDTH |
Sets window or control width. | yes | Percentage or pixels | (none) |