-
Notifications
You must be signed in to change notification settings - Fork 456
Windows 11 start button support #1222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
x64 version of pdbstr doesn't work (because of missing __CxxFrameHandler4 on Windows Server 2019). Fortunately it seems that x86 version works well, so we can use that one.
We are storing color settings in BBGGRR format (for historical reasons). This may be confusing for people that are used to (more widely used) RRGGBB format. Thus we will present color settings in RRGGBB format when editing. We will still use BBGGRR format for those settings internally. To maintain backward compatibility with existing settings stored in registry/xml. Also setting descriptions now contain hint about expected color format. This way it should be more clear what values `Open-Shell` expects. Fixes Open-Shell#82, Open-Shell#1141.
This way `Open-Shell Modern Settings` folder won't appear in File Explorer's frequent list. Fixes Open-Shell#744.
Multi-string settings have to be terminated by new line. Otherwise there may be some garbage (following the string) stored in registry.
Debug StartMenuDLL used to not find skins when put to Open-Shell installation folder. Now it will try to look for skins in default location (Skins folder in the same folder as DLL) and use alternative (Skins folder one level up) if not present.
- handling of `Taskbar alignment` setting (left/center) - start menu position is based on position of start button - mouse clicks to original button now work properly (without triggering original menu) - custom button is properly positioned - Win+X works properly
@bonzibudd Guys, any help with testing will be much appreciated 🙏 I was working on this for some time and testes what I could (including on Win7/Win10). |
When taskbar is hidden its window is moved off the screen (except for few pixels at border). It may happen that the taskbar window actually spans to another monitor (though still not visible). MonitorFromWindow API may thus return different monitor handle than the one visible taskbar is on. We will use GetTaskbarPosition function that correctly identifies taskbar's monitor by checking rectangle of visible taskbar. Fixes Open-Shell#908
Thank you ge0rdi! I will test this as soon as possible. Currently building the program since AppVeyor is down on my end. |
@bonzibudd |
@ge0rdi The menu positioning and the button integration seem to be working correctly, so I’m super happy about that. However, since around build 25217, the default Windows key is also overridden by the Win11 menu, so I think that will have to be fixed as well (I can provide more information if you think it’s worth diagnosing from an Insider build). I appreciate the addition of the version # in the context menu :) I also like the transition to RRGGBB for the color palette. Do you know if this will affect existing installs that have custom colors, or is it a purely visual change? For the skin changes, I didn’t find any issues with the skins I tested, but I will try some more when I have time. Maybe @CTVCAM8 can do some testing as well. Thank you again for this! |
I was focusing on standard Win11 22H2 build. But for sure would like to have a look at Insider as well.
The intent is to change visual representation only (the way how it is presented in settings). |
@ge0rdi Also, I noticed that the "Windows 10 Settings" item is still present on Win11, so we can rename that (if the option is still applicable on Win11.) Or, maybe it would make more sense to move it to the "Controls" tab since it seems redundant to have a tab dedicated to only one option. |
Yup, I know about this. It is unfortunate but I cannot do anything about it. If anybody wants to use custom icon, it simply needs to cover the original button.
I cannot verify whether it works for Win11 as I don't have multi-monitor setup with Win11 at hand.
Yup. I agree that it looks weird to have separate tab with just one option.
Looks simple enough. |
It is not a program that user will use explicitly. No need to show it in the list even if Windows tracks it as frequent program for some reason. Fixes Open-Shell#1164
It seems that Windows 11 prefers `Segoe Fluent Icons` over `Segoe MDL2 Assets` font. https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-fluent-icons-font Most of settings defined in `AllSystemSettings_{253E530E-387D-4BC2-959D-E6F86122E5F2}.xml` now refer to the new font.
@ge0rdi Other than that, I haven't found any other issues, but I might try ExplorerPatcher at some point to see if it has any issues, although I doubt it since it's based off of Windows 10 code. |
Yup, I guess that's expected (unfortunately). I will need to get touch enabled device so that I can debug and play with it. |
I guess I will merge this one. |
@bonzibudd |
plus many small improvements