@Jorge - It's probably worth testing the Windows 11 update on menu scaling.
I have a half-decant laptop that can do 3840x2160 and windows auto-scales it by 250%. It does interesting things with Winstep. You may wish to check it out if you have not already. In a default non-Winstep environment, it's ok. It does some interesting things with the Winstep menus (by exactly half). So maybe your own scaling can bypass that because the Engine-room DPI has a zero effect? I do not know enough how you've coded it which is why I suggest you have a look at it.
I simply downscaled to half (1920x1080) and zero issues, but the new update did a painful auto-scale. So it is both a request and an issue in one I guess, not of your doing. End-user can manually turn it off in Windows settings/Personal/Startmenu but that's not the point. I figure there might be a way you can stop it from auto-rescaling Winstep menus? Who knows?

I've split the topic since this seems to be about an issue and not exactly a wish for a new feature.

Anyway, I need screenshots to understand what you are trying to explain, sorry. If you change the screen DPI the size of menus, shelves, docks, etc, will also change with it, unless you have disabled automatic scaling on high DPI settings for any of those elements.

It will eventually adjust but it's ugly. LAPTOPS with Hi-res GPU options and capabilities are the issue. Winstep disable DPI does not fix. Menu's thin down in Width to half their size (Makes sense if Resolution is exactly double). I can go into the wst and double the button text width but that's silly. That is why I said I simply set it to 1920x1080. The modules resize fine automatically, menu's do not. If you do not set it to something other than auto and disable its recommended settings from taking over on any GPU detection changes on Windows updates in Windows itself, the final screenshot will always do the recommended setting on a GPU driver update. The end-user will then have to redo it all over again and all the module positions reset, so they'll have to re-position every module in every theme. It's not fun. I am pretty sure you may not wish people to have it look like the first shot and redo all their module settings.

P.S. at 3840 pixels, the recommended screen size is 250% so you can see it's exactly double. I can get around it but a lot of people probably won't want to.

Andrew, you talk about menus and I ask you for screenshots displaying the issue (i.e. what the expectation is vs. what it actually is) and none of your screenshots display a single menu (first screenshot shows a floating NextSTART taskbar, but how is that related to menus?!)! Sigh.

Or are you talking about the NextSTART taskbar and NOT the menus? If so you've got to start calling stuff by their actual names, because I just wasted time double checking the code related to menu DPI settings and I didn't find anything wrong lol

Besides, unless you actually find something that definitely isn't what it should be (i.e. a bug) stop worrying about how the theme looks at different screen resolutions/DPI settings, that is not the theme author's concern (not to mention the user might be running a combination of settings where some Winstep objects honor current screen DPI and others don't, and you have no control over that).

Jorge - I have reset my module settings four times trying to get around it and I won;t do it again with 48 themes, it's too painful. Nexus is a small part of the problem. Lost in translations....


OK - This says it all and unlike Nexus which as I said eventually resets - BUT - the menus and having to reset everything manually like it is a fresh installation does not.
The pictures say plenty.
I won't be saying anymore. If yo udo not think it is an issue then fine.

Changed to 1920


Default as per above image in my prior post at 3840

I'm just trying to understand what the issue is.

So, to make sure I got this right, first screenshot is screen resolution 1920x1080 at 100% DPI, second screenshot is 3840x2160 at 250% DPI, right?

The problem *seems* to be (but might not be that at all) that the max width set for the menu is not being upscaled as it should.

However the correct term is that the width of the menu on the first screenshot (1920x1080) is the CORRECT (native) size, but the width of the menu in the second screenshot (3840x2160) should be 250% (2.5 times) wider than in the first screenshot BUT IT IS NOT. It's wider, but obviously not 2.5 times wider as it should be.

I don't think this is an issue with the ButtonMaxWidth setting, I think it's something else, but I need that theme to make sure.

The theme is in the latest Gallery uploads "Orchestra" and a few new ones (I'm doing them alphabetically [mostly]).

As my last ditched attempt to find the issue outside of Winstep, I contacted nVidia support. I use Radeons on the desktops but the laptop has an nVidia GPU... that is the only difference.

As I anticipated, they will not say directly much other than they have had a few minor issues with the latest win 11 updates with some of the automatic start menu scaling additions... Keep in mind Windows 11 latest update menu (why I included the first images) - INCREASES its size if you select anything other than the default layout. This means to me as a 'layman', that they have included another auto-resize on the menus that may, or may not be compatible that seems to be different to the auto % scaling for the desktop. This is how it seems to me and the only reason I included all the various scaling shots.

Honestly, it would not surprise me if it is the nVidia driver because it wouldn't be the first time. They're all the same, none of them will truly own it if it is their issue anyway. I tend to prefer Radeon as first choice but the laptop came with nVidia (it was a gift).


I hope 'some' of that helps. BEING CLEAR - It squashes every menu to half of its width at 3840x2160 + 250%, not just the one you asked for.
I think it's also probably worth mentioning that my 5120x1440 Ultrawidescreen has zero issues and scales/auto-adjusts without doing anything - beautifully.
The only pain with that is I have had to make additional widescreen wallpapers because it isn't 16:9 or 16:10.