One of the reasons I started this project in first place is that I remembered the somewhat overhauled Disk Cleanup app in Win8 build 7850. It's actually a bit less impressive than it seems. It's pretty much Yet Another COM Wrapper™ that attempted to make it a little less chaotic
-
Show this thread
-
Microsoft also recently implemented similar functionality into the Windows 10 Settings app. To whomever had the luck of working with this pile of backwards compatibility hell, I empathize with you.
1 reply 0 retweets 5 likesShow this thread -
Besides learning a lot about Disk Cleanup (which on its own encompasses a "fun fact," did you know the actual feature name is Empty Volume Cache?) I also learned a lot about Windows Forms while working on this project. Who would've thought that scaling icons and lists sucks?
1 reply 0 retweets 6 likesShow this thread -
If some of you happen to be interested in the source, I'd love to hear your reactions once its out. The sheer amount of possible paths for obtaining the name, description, and icon for a cleanup handler is baffling and nothing's there to hold your hand. Just gotta iterate through
0 replies 0 retweets 6 likesShow this thread -
Replying to @WithinRafael
Currently the app uses ExtractIconEx and the resulting handle is then used with the help of Icon.FromHandle. The result of that gets put into an ImageList. What should I take care of to make sure handle leaking isn't happening?
0 replies 0 retweets 0 likes -
Replying to @WithinRafael
Thanks a lot for the heads up. Did MS ever explain why Drawing Icons happen to be like this?
0 replies 0 retweets 0 likes
You can also share HBITMAPs with some undocumented trickery
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.