Hollywood forum

tolkien wrote:But It would be like when a program needs an external library. Once the player is installed you forget about it.

The Hollywood-Player should become part of the AmigaOS4-Package, maybe within AmigaOS4.2?
And then of course autoupdated with Amiupdate, if Andreas publish new Updates to the Player.

@fingus: The idea of a freely available Hollywood Player is still in my head and I'd really like to see it realized someday. Then everybody could just ship a single applet for all the platforms Hollywood supports, much like an SWF file. I wait for this day impatiently 8-) Concerning Hollywood's rep...

It´s not working within the script, using the @screen-preprocessor-command and leads always to a 640x480-Screen/Window. This seems to be the only way to open a Fullscreen with the Host-Resolution, but it has the big disadvantage, that you have always a second window named "Hollywood" in 640x480 ope...

An interesting option would be a build in Hollywood-Player in AmigaOS4.1. So everybody can use the very much smaller .hwa (Hollywood-Applet-Files) as executables. And that would be very competive to the small native apps that were compiled with the AmigaOS-SDK/Compiler. I see it often in several Ami...

Should already be possible by specifying 0 in SCRWIDTH and SCRHEIGHT arguments, i.e. Hollywood file.hws -scrwidth 0 -scrheight 0 It´s not working within the script, using the @screen-preprocessor-command and leads always to a 640x480-Screen/Window. This seems to be the only way to open a Fullscreen...

It´s working now, don´t know why.

I assume it was my fault (bad code).

You can delete this whole thread.

Begindoublebuffer

and

Flip

seems to do nothing like a black screen on a Lenovo Tablet 10.1 Device.
This device have a nvidia tegra graphics chip.

I got sometimes problems with Downloadfile() on WIndowsXP-Executables too.

Better later then never:

This Thread was intended to be in Board Index > Hollywood > Wishlist

My fault

On OS4 it depends if its working on this:

The controller have to be configured with AmigaInput-Prefs to one low-level-port.
Once configured, it works, but AmigaInput isn't that stable sadly, so in some cases it can fail.