Using Classic-Shell on Windows 10 (MS Surface Pro 7), and Open-Shell on Windows 11 (MS Surface Laptop Studio 2).
This was not an issue on Classic-Shell. Could be a change in Windows, unsure.
Basically, in the older setup, there is no distinction whether I click the start button with a mouse, or tap it on the touch screen. Classic-Shell would open the classic menu skin.
With the newer setup, I just noticed if I tapped the start button with the touch screen, the original Windows 11 Start Menu appears. Thought Open-Shell didn't autostart following a computer restart, only to discover it was running as per expected, but that there is a difference in behaviour whether the user clicked the start button or tapped it via touch.
Might be nice to let the user decide what the start button does, depending on if they click or touch, but I don't believe this is considered as a feature yet.
Area of issue
Start menu
To reproduce
On Windows 11, running Open-Shell Menu 4.4.191:
Click Start button; Open-Shell Menu Skin appears.
Tap Start button (using touch screen PC); original Windows 11 Start Menu appears.
Expected behavior
Was hoping the Open-Shell Menu Skin functioned agnostic to how the user evoked the Start button.
Describe the bug
Using Classic-Shell on Windows 10 (MS Surface Pro 7), and Open-Shell on Windows 11 (MS Surface Laptop Studio 2). This was not an issue on Classic-Shell. Could be a change in Windows, unsure.
Basically, in the older setup, there is no distinction whether I click the start button with a mouse, or tap it on the touch screen. Classic-Shell would open the classic menu skin.
With the newer setup, I just noticed if I tapped the start button with the touch screen, the original Windows 11 Start Menu appears. Thought Open-Shell didn't autostart following a computer restart, only to discover it was running as per expected, but that there is a difference in behaviour whether the user clicked the start button or tapped it via touch.
Might be nice to let the user decide what the start button does, depending on if they click or touch, but I don't believe this is considered as a feature yet.
Area of issue
Start menu
To reproduce
On Windows 11, running Open-Shell Menu 4.4.191:
Expected behavior
Was hoping the Open-Shell Menu Skin functioned agnostic to how the user evoked the Start button.
Open-Shell version
4.4.191
Windows version
Windows 11 (Home) 23H2
Additional context
No response