Using the CODM and the new facilities in HW4 to define alternative screens, I find that although screens appear to switch correctly to the required layouts, depending on whether I use a 4:3 screen or a 16:9 screen, in widescreen mode, there is a black border all the way round my background image and I can't place stop icons past the end of the background and over the black border. Is there any way to make Hauptwerk "claim" the entire area of the black border?
Here's typical code for the background:
****************************************************
<CustomDisplay_AlternateLayout1_ConsoleWidthPixels>1350</CustomDisplay_AlternateLayout1_ConsoleWidthPixels><CustomDisplay_AlternateLayout1_ConsoleHeightPixels>666</CustomDisplay_AlternateLayout1_ConsoleHeightPixels>
****************************************************
<AlternateLayout1_Include>Y</AlternateLayout1_Include> <AlternateLayout1_BackgroundImageFilename>ParamountImages/RosewoodW.png</AlternateLayout1_BackgroundImageFilename>
****************************************************
The console image file and the rosewood background file are both 1350 x 666 pixels.
It doesn't seem to matter whether the figures or the size of the actual background image files are increased, HW just scales back to sit inside its enforced border.
The standard 4:3 layout remains unaltered with no enforced border.
Also, when using the alternative screen switch in the ODF, it makes the organ much slower to load, even on an images only ODF. With the switch off and no alt screen positions defined, loading (images only) is almost instantaneous. Whilst I realise that there will be position calculations needed, it does seem to take rather longer than expected. This is also the same when loading outside the compiled ODF outside the CODM. Would it be possible to have the positioning cached, so that at least loading an organ in normal user mode would be much faster?
Here's typical code for the background:
****************************************************
<CustomDisplay_AlternateLayout1_ConsoleWidthPixels>1350</CustomDisplay_AlternateLayout1_ConsoleWidthPixels><CustomDisplay_AlternateLayout1_ConsoleHeightPixels>666</CustomDisplay_AlternateLayout1_ConsoleHeightPixels>
****************************************************
<AlternateLayout1_Include>Y</AlternateLayout1_Include> <AlternateLayout1_BackgroundImageFilename>ParamountImages/RosewoodW.png</AlternateLayout1_BackgroundImageFilename>
****************************************************
The console image file and the rosewood background file are both 1350 x 666 pixels.
It doesn't seem to matter whether the figures or the size of the actual background image files are increased, HW just scales back to sit inside its enforced border.
The standard 4:3 layout remains unaltered with no enforced border.
Also, when using the alternative screen switch in the ODF, it makes the organ much slower to load, even on an images only ODF. With the switch off and no alt screen positions defined, loading (images only) is almost instantaneous. Whilst I realise that there will be position calculations needed, it does seem to take rather longer than expected. This is also the same when loading outside the compiled ODF outside the CODM. Would it be possible to have the positioning cached, so that at least loading an organ in normal user mode would be much faster?
Regards,
Alan.
(Paramount Organ Works)
Alan.
(Paramount Organ Works)