Flash
Player 4 for the Pocket PC (Developer Release)
release notes
This document addresses issues that are not discussed in
the Flash documentation and may be
updated as more information becomes available.
Overview
This
is a "Developer Release" designed to give developers access
to the Macromedia Flash Player 4 for Pocket PC. The notes below are
intended to help developers learn some of the nuances of this exciting
new Flash Player platform.
System
requirements
| |
| Processor |
MIPS
r4000 |
SH3 |
StrongARM |
Pocket
PC
Device Models |
Cassiopeia
E-125 |
Jornada
548 |
iPAQ 3650, iPAQ 3630 |
| RAM |
32MB |
32MB |
32MB |
| Requires
Color Screen |
yes |
yes |
yes |
Issues
 |
Some
Flash 5 content will not play.
The Flash Player
4 for Pocket PC will not play any Flash 5 content. Specifically,
Flash 5 movies that use ActionScript are not compatible
with this player. All pre Flash 5 content will play as
expected.
Note: A Flash 5 SWF embedded
in HTML will show as a blank white rectangle. |
 |
The
contextual menu is disabled.
This allows drop and drag functionality to be implemented more easily
in the Microsoft Pocket PC environment.
|
 |
Spawning
a new browser instance is not possible.
That is, there can only be one instance of the browser open. This is
a limitation of the Microsoft Pocket PC OS.
|
 |
Printing
is not supported.
This is due to limitations in the Pocket PC OS.
|
 |
MP3
playback is disabled.
ADPCM
sound is however an option.
Note: When publishing
to the Flash Player 4 format, the Flash 5 authoring tool will
convert Published SWF files to use ADPCM sound even if MP3
is selected. |
 |
The
default quality (anti-aliasing) is Medium.
High
quality is not available due to target platform performance
limitations. Using HTML to set the quality to High or Medium
will cause the Flash Player 4 for Pocket PC to play in Medium
quality. (Low quality still equals Low quality.)
|
 |
FSCommand
is not supported by Pocket Internet Explorer.
The
ActiveX interface to implement this in Pocket Internet Explorer
is not supported in this release. |
 |
HTML files generated
with the Publish command from the Flash authoring tool will
not load Flash movie files.
The manual workaround is to Publish and then manually edit the HTML file.
Replace "<OBJECT classid=" with "<OBJECT id="id" classid=". This
will allow Pocket IE to instantiate the Flash 4 Player for the Pocket
PC. A more automatic solution is to use the template on the Macromedia
Exchange for Flash. |
 |
Scaling
does not always work as expected.
| 1 |
Microsoft
Pocket Internet Explorer ignores the "%" when defining
width and height in the HTML embed tag. For example,
defining "width=100% height=100%" is the same as "width=100
height=100". In most cases, this is not a desirable
result. |
| 2 |
When
using the Scale parameter that passed from HTML to
the Flash movie with values such as "noborder", "showall",
or "exactfit"), the resulting SWF does not scale
properly. |
| 3 |
Pocket Internet Explorer will not display Flash movies
when the embed tag defines width and height that
ignore the Flash movie's original aspect ratio.
For example, a SWF that is 200 x 200 pixels will
not display is the embed tag defines width=50 and
height=175. |
|
 |
Detection
of the version and type of Flash Player 4 for Pocket PC will
not work using VBScript or JavaScript.
For details on version detection see the following Flash
TechNote (ID 14294). |
 |
To
view some large movies, users will have to configure their
device memory system resources.
Microsoft Pocket
PC should do this automatically in most cases until it runs out
of memory. Please refer to Microsoft Pocket PC documentation.
Notes:
 |
If a movie causes
the memory to be used up, some bitmaps may have random
or missing graphics. |
 |
Deleting
unused files to free up space will help avoid memory
crunches. For example, clearing the Pocket PC Internet
Explorer browser cache will increase free space. |
|
 |
Many
desktop UI functions are different on Pocket PC.
| 1 |
After
a button is pressed, it remains on the rollover state
until the user taps the stylus somewhere else. |
| 2 |
Pressing
down the stylus does not invoke the OnPress event;
however, letting go the stylus does invoke it. |
| 3 |
Mouse rollover events are not handled correctly. In
general, they shouldn't be handled at all on
the Pocket PC platform. However, the OnRollover
event is processed while the stylus is released
which sometimes causes unpredictable behavior
in some Flash movies authored to handle the rollover
event. |
|
How to report bugs
Find a bug? Please send
an e-mail to the Flash Player for
the Pocket PC team with the following information:
=======================
Your Name:
Your E-mail:
Your Phone:
=======================
Bug Description
=======================
Summary:
Steps to Reproduce:
1.
2.
3.
Expected Results:
Actual Results:
=======================
Platform:
=======================
Cassiopeia PocketPC________
iPAQ PocketPC________
Jornada PocketPC________
=======================
System Information:
=======================
Hardware:
OS Version:
RAM:
=======================
Please be
sure to put Bug Report: [very brief summary of problem] in the Subject
line, so we can tell the bug reports from the feature requests. For
example, "Bug Report: Flash movie files disappear after one play". |