Horizontal Position Offset not working after newest update

[RustedEmber]

Describe the bug

I used to be able to type a negative number to move the whole start menu to the left off screen, but it no longer does this. Now it only registers 0 and higher positions.

Area of issue

Start menu

To reproduce

1. Go to settings
2. Search for horizontal
3. Modify the horizontal offset to a negative number, ex: -10.
4. You see that the start menu behaves as if you put a 0 in the field.

Expected behavior

The start menu to move to the left with negative numbers.

Open-Shell version

4.4_190

Windows version

Windows 10 22H2

Additional context

No response

[ge0rdi]

I used to be able to type a negative number to move the whole start menu to the left off screen

So you want to like hide part of the start menu (put it off screen)?
Wondering what's the purpose of that.

Now it only registers 0 and higher positions.

I can confirm. And I see where the problem is (part of changes due to Windows 11 center aligned taskbar support).

[jfgimenezx]

Hi,
I have the same problem. It always left a margin of 9 pixels.
It did so before, but I had a value of -8 in "Horizontal position offset" and worked fine. Now it doesn't accept negative values :-(

[ge0rdi]

@jfgimenezx
What version of Open-Shell do you use?
Does the same happen with some of standard skins (like Metro or Immersive)?

[jfgimenezx]

1. 4.4.190
2. Other skins haven't show that margin (it seems an issue for "Fluent-Metro"), but negative values are not allowed too. ITOH, vertical position does accept any value, including negative ones:
   
   

[ge0rdi]

it seems an issue for "Fluent-Metro"

It seems to be caused by Menu border style set to Floating (in Fluent-Metro skin settings).
That one adds some vertical/horizontal offset to the menu.

You can eventually set it to Classic as a workaround.

vertical position does accept any value, including negative ones

There is similar problem for vertical offset, but it gets visible with vertical taskbar.

I'm looking into this and trying to figure out how to fix it.
Negative offsets are supposed to work, so current behavior is a bug.

[jfgimenez]

Thank you very much!

[ge0rdi]

Guys, you can try with fixed build from #1636 PR.

[jfgimenez]

Guys, you can try with fixed build from #1636 PR.

Now it works fine!

Thank you very much!

[ge0rdi]

Fixed in 4.4.191.