[BUG] "Pixel maximum menu width" not working as expected

[chip33]

Description, Steps to reproduce, Expected behavior, Screenshots

I was hoping to put in a feature request to enable a "Pixel minimum menu width"
where you could set a minimum width and the window width would shrink to that size but expand if longer filenames were found in the directory.
This would be similar to how the Quick Launch menu works now expanding in width (to a set maximum) as the filename grows longer.

"Pixel maximum menu height" works as expected but changing "Pixel maximum menu width" between its limits of 50 to 1000 pixels has no visible effect on the STM window width which always looks like this.

Is this a bug in "Pixel maximum menu width" ?
If you feel that adding a "Pixel miniimum menu width" is a good feature I could convert this to a request later.
Thank you for all your work on this project!

[Hofknecht]

With "Pixel miniimum menu width" i am not sure, for me it is enough that minimum is smalles text and there is a fixed minimum, you can see e.g. here

related to bug in "Pixel maximum menu width", i set e.g. 900 made a short test with 'XXXXX...' and seems to work

(there is a known issue that measure string is not perfect accurate e.g. when using lllllllll it measures too short, but for X it probably measures a little bit too much)

when i reduce to e.g. 150 it looks like this

so basically should work.

What is it configured in your last screenshot and does it not change anything when you change the value?

[chip33]

Ah yes, thank you for your screenshots they are really helpful.

Turns out it is only an issue at high resolutions.

I tried it at 1080p and everything works perfectly and the window shrinks very narrow to fit short filenames like in your images and expands hugely to fit long filenames.

At 4k (at 300% scaling) for some reason Windows stops the window from shrinking below about 800px
As the maximum pixel width is 1000 there is almost no difference.
At 350% scaling the STM window never shrinks below 1000px so there is no difference at all.

Making the maximum width go above 1000 which is only 1/4 of the screen would show that it is working.
The not going below 800px even when set to 100px width may be a windows scaling thing rather than a setting in STM, I am not sure.

4k @ 300% display scaling 100px maximum width:

4k @ 300% display scaling 1000px maximum width:

4k @ 350% display scaling 100px maximum width:

4k @ 350% display scaling 1000px maximum width:

[Hofknecht]

@chip33
solved with 1.2.6.4

do you want to test it and check if it works now as expected?
do you still want to configure a minimum width?

[chip33]

Thank you very much for looking at this.
The issue of it not going above 1000px width which is needed for 4K is fixed and tested.
The issue of it not going below ≈ 800px at 4k @ 300% display scaling and 1000px at 4k @ 350% is still there.

The major issue has been fixed but it would be nice if the window would shrink to fit the filenames in 4K as well.

This is the minimum width it will shrink to at 4K 350% scaling:

[chip33]

Maybe windows is multiplying the minimum width by 350% and that is why?
In that case changing the minimum width could help.

[Hofknecht]

@chip33
Thank you for testing.

We made 2 mistakes at the redesign 1.2. Now we also tested correct, was a bit tricky with normal screens to test 350%. : )
now should be solved
can you try again?

[Hofknecht]

@chip33
If you notice any other 4k scaling problems, please feel free to create issues for them.
Even if you still want to set a minimum size you can just create an issue

[chip33]

Thank you so much, great job finding this :)
The whole issue is solved.

Here it is working now at 4k 350%