The "Settings" Window is not displayed well If the Taskbar is on the Top of the Screen

[spaceman5]

Hi all


I use Windows 10 Home edition.
On my Windows, I set the Taskbar to be on the Top, instead of the default which is on the bottom of the screen.


Now when I run OBS, it runs well,
but when I open the "Settings" Window, it seems that there's a tiny visual bug.
The "Settings" Window is displayed, but the bottom part of that window, including the buttons on the bottom, are out of the Screen..

Please have a look:

If the window was shown with a slightly smaller Height,
then the Buttons on the bottom of it would've been visible.

If this can be fixed, it will be great.


Thank you

 

[Banyarola]

Use the scroll bar on the right to scroll down...

 

[spaceman5]

Hi Banyarola

the Scrollbar affects the Setting controls, like all the Checkboxes etc.
The buttons on the bottom (to Accept/Cancel) are not affected by the scrollbar.
And as can be seen, they are out of the screen, because the window extends out of the screen.

So this workaround, unfortunately, will not help overcome this.

The function that calculated the Window's Size and Position is the way to solve this..

 

[Banyarola]

I can't help you...
If you don't get help soon repost the problem...

 

[spaceman5]

I can't help you...

It's ok..
Thank you for trying.

The developers are reading the posts in this forum,
so hopefully it will be fixed in one of the next versions.

BTW,
today I noticed that it happens in more windows that OBS opens, and not just in the Settings window.

I will capture screenshots of the other windows, and post them here,
so this small visual bug can be fixed together across all of the windows.

 

[WBE]

Apparently the available height for popup menus is based on the height of the screen, rather than on screen height minus taskbar height. (It is neither the client area since the OBS Studio title bar is covered by those menus, as expected.)

It's a bug (as this is not standard Windows behaviour) and it's bit annoying, but the simple workaround is: View, Fullscreen Interface (F11)

 

[spaceman5]

Nice workaround, thank you very much :)