Maximizing screen real estate
Maximizing screen real estate
I'm working on a CODF and would like to eliminate the black borders I'm getting around my background image and graphics so that I can use all of the pixels not occupied by HW's user interface. Is there a way to do this? I'm running on a 1920x1080 screen and it looks like right now I'm only getting to use about 1875 x 800 pixels. It looks like there's a permanent 20 pixel black border around anything I create.
Re: Maximizing screen real estate
The CODM document that comes with Hauptwerk talks about this a bit, I think, Hauptwerk needs to leave a portion at the bottom that will be black for the standard buttons like the general cancel, so the true "available" aspect ratio is somewhat wider and shorter than what it seems.
Next, Hauptwerk is only able to accommodate a certain size of background, I forget the exact measurements, but they're written in the CODM document, I believe. Anything larger than this is automatically rescaled to fit the resolution it supports. So you might be getting something funny with the rescaling.
So what I do is make the background just as wide as Hauptwerk supports, but a fair bit shorter to accommodate the menu bars. That means it won't be resized, and it usually fits the whole screen. Maybe Martin will have more to say about this though!
Next, Hauptwerk is only able to accommodate a certain size of background, I forget the exact measurements, but they're written in the CODM document, I believe. Anything larger than this is automatically rescaled to fit the resolution it supports. So you might be getting something funny with the rescaling.
So what I do is make the background just as wide as Hauptwerk supports, but a fair bit shorter to accommodate the menu bars. That means it won't be resized, and it usually fits the whole screen. Maybe Martin will have more to say about this though!
Re: Maximizing screen real estate
Hello mdl,
To add to larason2's reply (thanks very much, larason2):
If the "View | Zoom virtual console to fit (for this organ)" option is turned on (as it is by default), Hauptwerk will scale the ODF's virtual console rectangle linearly (and equally in both directions, so as to preserve its aspect ratio) so that it fits the available screen area as best as possible, subject to the fact that it will always leave a black border of at least 24 pixels (for Hauptwerk v9+; it was 48 pixels in previous versions), but no more than that, unless needed on sides where a difference in aspect ratio requires it.
The 24-pixel black border is intentional, and you can't override that from your ODF. It's also intentionally small (only 24 pixels), so as to avoid wasting screen space.
To add to larason2's reply (thanks very much, larason2):
If the "View | Zoom virtual console to fit (for this organ)" option is turned on (as it is by default), Hauptwerk will scale the ODF's virtual console rectangle linearly (and equally in both directions, so as to preserve its aspect ratio) so that it fits the available screen area as best as possible, subject to the fact that it will always leave a black border of at least 24 pixels (for Hauptwerk v9+; it was 48 pixels in previous versions), but no more than that, unless needed on sides where a difference in aspect ratio requires it.
The 24-pixel black border is intentional, and you can't override that from your ODF. It's also intentionally small (only 24 pixels), so as to avoid wasting screen space.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Hauptwerk software designer/developer, Milan Digital Audio.
Re: Maximizing screen real estate
I am aware of the need to reserve space for the standard buttons like general cancel. It's the mandatory 24-pixel border that Martin mentions which I'm asking about. What purpose does that black border serve? Why can't I fill it with whatever background image I am using for my design?
Since I'm using V8 at the moment, perhaps I should prioritize upgrading to V9. I think I'm getting 24 pixels on each side. If V9 reduces that to 12 on each side (24 total in each dimension), then that would be an improvement at least.
Since I'm using V8 at the moment, perhaps I should prioritize upgrading to V9. I think I'm getting 24 pixels on each side. If V9 reduces that to 12 on each side (24 total in each dimension), then that would be an improvement at least.
Re: Maximizing screen real estate
Like Martin and I said, it's because of the resizing. Resize the background so it won't have to be zoomed, and the problem will be solved. I ran into the same issue, and that's how I solved it.
Re: Maximizing screen real estate
What you pointed out was the need for black bars in only one dimension in order to preserve aspect ratio. That I understand. The part I don't understand is the mandatory 24-pixel black border outside of that which Martin mentioned. I'm wondering why that is desirable.
Michael
Re: Maximizing screen real estate
It's not desirable, but that's how the program works. Personally I don't think it's a big deal. Every program has limitations.
Re: Maximizing screen real estate
I understand that no software is ever going to be perfect. But as a software engineer, I am wondering why this particular limitation exists. I would expect to provide the entire window area to the ODF for whatever use the current organ definition has for it.
Michael
Re: Maximizing screen real estate
Hello Michael,
It's correct that upgrading to v9 halves the width of the black border (in the relevant dimension).
The border is intentionally visible on all sides, for aesthetic/clarity reasons (to separate the virtual console from the control panels, etc.), and it isn't something that we would want to eliminate, I'm afraid. However, it's intentionally very thin, so as to minimise use of screen space.
It's correct that upgrading to v9 halves the width of the black border (in the relevant dimension).
The border is intentionally visible on all sides, for aesthetic/clarity reasons (to separate the virtual console from the control panels, etc.), and it isn't something that we would want to eliminate, I'm afraid. However, it's intentionally very thin, so as to minimise use of screen space.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Hauptwerk software designer/developer, Milan Digital Audio.
Re: Maximizing screen real estate
I upgraded to v9 and was pleased to see the black border get skinnier as expected. Aesthetically, I still think it should be eliminated, but I appreciate at least seeing its width reduced from 4.4% of my vertical screen real estate down to only 2.2%. Thanks for the explanations and the improvement in v9.
Re: Maximizing screen real estate
Thanks very much for upgrading, Michael, and glad it's more to your taste now.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Hauptwerk software designer/developer, Milan Digital Audio.