Repository navigation
Conversation
|
was this generated by AI? |
|
AI assistance was used during development, yes. That being said, I have a good understanding of the code I am submitting and can defend it, as it is nearly entirely based on the existing implementation of the Windows 11 network flyout. |
|
Hi. I'm on 22621.4317 and
Is that what you get in 25281+? If yes, please broaden the checks because I want Nickel (226xx/22H2/23H2) to stay supported. You can tell your AI to scan the binaries in https://winbindex.m417z.com/ to get the precise build range. |
|
Yeah, that is what I'm getting. The check I added is wrong; I'd traced the addition of the I had the AI look into it more with the resource you pointed me to, and it claims the first trace of the So far I've successfully tested and found it working down to 22621.2506. My main problem right now is at how the strings clearly exist in some older builds (22621.2215...22621.2428), and yet, the routing to the Control Center works but the routing to the specific Sound output page does not. I'll keep looking and try to further narrow it down, as well as accurately find and explain why it isn't working on the other builds, and what the actual condition for its existence is. |
|
Update: The AI and I are done investigating, and have successfully limited the checks to revision >= 2506 for Nickel (22H2/23H2), and any build higher than 25281 (so all builds after that, predating 24H2, and every 24H2 and higher build). Scanning the binaries in winbindex, the AI found evidence of While the AI was doing this scan, I also had a look at Microsoft's support page for updates, and it seems to somewhat corroborate this. These two updates (KB5031455 / 2506 and KB5032190 / 2715) mention in their highlights the addition of the volume mixer, and the WIN + CTRL + V shortcut whose presence inspired me to try and add it as a sound flyout in the first place, so it makes sense to me that this is when this path was activated. I have added an |

Closes: #2454, #4980, possibly #792 (though not for the reason mentioned)
Partially addresses: #1451
Add the "Sound output" flyout from Quick Settings (Control Center) as a "Windows 11 flyout" option for the sound icon of the Windows 10 taskbar's system tray, done in a similar manner to how flyouts are implemented for the Network icon (specifically, IAT patching the
CoCreateInstanceimport insndvolsso.dll).The flyout is accessed via
ms-actioncenter:controlcenter/volume, which first appears in build 25281 (tested and confirmed). Checks have been added to ensure the option does not appear in builds below 25281.