If you assume that DemoX is only used on a Web page then these limitations
make sense. They also make sense if by removing these features the control
is smaller and thus faster to download. However, if DemoX is used in an
application then these features should not be removed.
So, as a wish to the developers, perhaps these features could be returned.
Another feature I would love to see added: the ability to raise an event.
The Macromedia Flash program has the FS event where you can pass two
parameters: the command and the data. That works very well. It is an
excellent way to pass user and timing information from the demo to the host.
At the moment the only information passed up to the host is the name of the
slide - which can be used to pass information, however it is not ideal. As
an alternative, perhaps you could simply create a "user" property that could
be monitored by the host program, and set by the demo.
While you are at it, why don't you allow the DemoShield demo to write to the
registry. I was very impressed to be able to read the registry, but I would
also like to be able to write to it.
The DemoShield program has a number of great tools and options that make it
excellent for applications outside the traditional "product demo" area. It
just needs a few small changes to make it a little more flexible from a
programming standpoint..
Jason Tranter