CloneWb Screen
Posted: Fri Oct 25, 2013 10:43 am
Title says it all!
Code: Select all
Hollywood file.hws -scrwidth 0 -scrheight 0
The Cross-Platform Multimedia Application Layer
https://www.hollywood-mal.com/forums/
Code: Select all
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.Andreas wrote:Should already be possible by specifying 0 in SCRWIDTH and SCRHEIGHT arguments, i.e.
Code: Select all
Hollywood file.hws -scrwidth 0 -scrheight 0
Code: Select all
SetDisplayAttributes({title=#VERSION, width=1600, height=1200, Layers= True, scalemode=#SCALEMODE_LAYER, Smoothscale=True, scalewidth = GetAttribute(#DISPLAY, 0, #ATTRHOSTWIDTH) , scaleheight = GetAttribute(#DISPLAY, 0, #ATTRHOSTHEIGHT), hidden=True })
ChangeDisplayMode(#DISPMODE_FULLSCREEN, GetAttribute(#DISPLAY, 0, #ATTRHOSTWIDTH), GetAttribute(#DISPLAY, 0, #ATTRHOSTHEIGHT))Now I'm confused... you want to clone the Workbench screen but you mention Windows in the same context? You know that no other operating system supported by Hollywood has the concept of screens, right? The screen concept is really unique to the Amiga.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 open on Windows:
Well, there is of course a rationale behind this design. The preprocessor commands like @DISPLAY are for compile-time definitions whereas commands like SetDisplayAttributes() are for run-time changes to an existing display. The @SCREEN preprocessor command specifies the initial screen mode for the entire script. It is not possible to merge this with the @DISPLAY preprocessor command because on Amiga systems, there could be multiple displays on a single screen. Of course, on systems like Windows the @SCREEN doesn't really make sense and could be merged with @DISPLAY but on AmigaOS it's not that easy.In general, it´s very confusing having this several commands like Setdisplayattributes, changedisplaymode, @screen, @display...etc.
I know it´s for compatibility-reasons, but it´s confusing for the coder!
Sorry, i have forgot to mention that i did a programm that should run on Windows AND Amiga with the same codebase. And in that case i have experienced this second window on Windows appering what is really disturbing and looking unprofessional.Andreas wrote:Now I'm confused... you want to clone the Workbench screen but you mention Windows in the same context? You know that no other operating system supported by Hollywood has the concept of screens, right? The screen concept is really unique to the Amiga.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 open on Windows: