Using Segoe Fluent Icons font

[krlvm]

Is it possible to use the new Segoe Fluent Icons instead of Segoe MDL2 Assets for system tray icons?

[valinet]

Yeah, it's possible. I was using some code made mostly from code decompiled from SAB some time ago and it worked.

The problem is, it's ripped straight from the decompiled binaries... not to mention it needs some refining to be shipped, but it's also questionable whether to ship it. For the moment, it sits in a private header file. There are mentions about it in the source code as well. I don't actively use it at the moment, it's too hard to test with that for 2 slightly different icons basically, and I can live without that just fine. There was some thread discussing this a while ago: #71.

Other interesting things regarding graphics can be made as well, like replacing the search, widgets and task view buttons icons on the taskbar. This one needs some additional bits to have it ready for shipping as a release, like, grabbing the icons automatically from the "pri" resource files in the system (they are in SVG), and making scaled versions from those using Windows Imaging Component, for example, at runtime, so we avoid shipping copyrighted binaries, but rather use the ones on the user's system, which are shipped by the OS; again, check the source code, there are some mentions about it:

Similarly, maybe even the Start button image could be changed...? Idk, haven't looked on that specifically, but probably with something along these lines (hook SHCreateStreamOnModuleResource in explorer.exe and provide a stream containing a different icon). The problem, again, is creating scaled versions, so it works properly on different DPI screen etc. Some boilerplate work and quite some support infrastructure around it, that's how graphics work is.

Anyway, a clean room and tested implementation would be the best regarding this. Otherwise, idk what to really say about this. I personally do not care about graphics that much, so I will leave it up to the community to come up with a production-ready implementation for these things.

Thanks