NoelC

Yes, I mentioned that above. I've already integrated it into my own software, for version reporting. -Noel

Not that I haven't already posted screenshots, but I suspect that if Microsoft took notice of them they'd just take steps to block the kind of work BigMuscle is doing. They really do think they know better. -Noel

That's interesting. Can you be more specific about what you want to do? I assume you're trying to do more than just enable copying to and from their servers via the browser. I don't seem to have any problem with doing just that. I use only a local account and I've scoured my system to disable all kinds of integrated SkyDrive/OneDrive stuff. Seems like I've had to work pretty hard to find and disable an awful lot of drivers, extensions, etc. for something that apparently doesn't work anyway with a local account. -Noel

Heh, earlier today I created another user on my Win 10 test setup for some unprivileged user testing of my own software (did I ever mention that I think UAC is a poor implementation of a bad idea?) and wow, I almost puked after having used Aero Glass and my replacement theme atlas on my normal Win 10 account. It really illustrates how far from "the norm" I configure my Windows systems to be. Doesn't Microsoft have ANYONE on staff with even the slightest bit of perceptive sensibilities? -Noel

Since Win 8.1 an older application manifested for use with a particular version and using the prior APIs always gets an indication via GetVersionInfoEx() that the operating system is the version it is manifested for. I guess Microsoft didn't want older applications second guessing the OS. See the following, for example: http://msdn.microsoft.com/en-us/library/windows/desktop/ms724451(v=vs.85).aspx If you really, really want to know what version you're running, Windows 8.1 and newer use a new means to determine the OS version: Version Helper functions. See: http://msdn.microsoft.com/en-us/library/windows/desktop/dn424972(v=vs.85).aspx The key thing is that they don't make IsWindows10OrGreater available in the SDK until that version is really available, so you can't really code an application to be compatible with a version of Windows not yet released, except that you CAN because they also provide a generic IsWindowsVersionOrGreater() function that you could run in a loop... Somewhere in all this it feels as though there is a nefarious motive, but I can't quite spot it. In any case, it seems like they could have spent time on something more important than coding all that. -Noel

ClassicShell does all that - very well indeed - and has done so since Vista. That's the point. I'd prefer Microsoft work on other SUBSTANTIAL features of Windows. We already have a perfectly good Start Menu in Classic Shell and Microsoft need worry no more about it. Their implementations have never been as good as 3rd party software, and there's no reason to expect that to change. -Noel

I haven't tried other settings 0, 1, or 2. You should experiment - maybe one of them will be "just right". -Noel

Sure , and the net result of this "vast" testing is Wndows 8/8.1 and now 10. LOL. And here I thought the previews were being released in order to herd hapless sheeple into liking what Microsoft says they should like. We see how well that's working. We're here in this very thread because "less is better" sometimes simply isn't. Patience my half-shaven friends. Progress on restoring sanity after Microsoft's snipping appears very good so far. Very good indeed. -Noel

Just to be clear, you cannot purchase this software. You may be afforded certain privileges to access advanced features such as automatic symbol download if you donate a small sum to the author. That's what many of us have done, and the donation-enhanced software does work with the latest update of Windows. Also keep in mind that there is a new version on the horizon. I don't know for sure, but it may provide a better "try before you donate" experience than the current 1.2.5 version does. My advice to you is to read the last few dozen pages of this thread. There have been a lot of questions like yours asked and answered. -Noel

Please read the 2nd post in this thread, megahjt. -Noel

They've clearly still got their heads every bit as far up their rears as they've been for 5 years now. Sinofsky/Ballmer have brought the future of computing to a 3rd world status, all the while piling up gargantuan personal fortunes. If CNN reports that they have choked on steak bones I won't shed a tear. It's going to take a bit more than playing with the UI animations to make a "threshold" level operating system, I think. Obviously they have no master plan, based on what we're seeing. It's more like a few guys fooling around with the Windows source code. Sad as it seems to be, the Windows era really does appear to be over. It's sputtering just too badly for too many years... 5 years since the release of the last decent OS, and frankly even Win 7 had its disappointments. Windows 8 was literally NO MORE than 7.1 with some basically dysfunctional tablet stuff tacked on and relabeling of "Hibernate" (around since way back) as "fastest Windows yet!". Now we have 10 which is really 8.2. What's next? 33.0 to show how amazingly far it's come? The BS is piling high indeed. It's getting to be enough to change the orbit of the Earth. Time for Wall Street to move in and cut them into little bits. -Noel

Thanks. I thought that. I just couldn't think what the 'w' could stand for. I'm guessing it was an abbreviation in your language. -Noel

Sorry for my ignorance, but what's "pw1"? -Noel

It's not just you; I see it too in build 9860 x64. -Noel

I wonder if Microsoft's symbol servers may be temporarily overloaded. Different members here saw the successful completion of symbol downloads for Win 10 at vastly different times. -Noel

I hope I didn't come off as too critical. Looking at my post it sounds that way. I've run across too many systems that are "cleaned" and otherwise poorly taken care of into the point of being toast, so I'm sensitive. -Noel

Sounds great. Just to make sure I understand you... You're saying that the custom inactive color will be able to be set with the next build via the ColorizationColorInactive DWORD value in the DWM key? That's the setting that I don't see do anything now, with the 1.2.6 beta for Win 10. -Noel

What does CCleaner buy you that you can't do yourself? I've always regarded "cleaner" tools as self-marketing snake oil. "Clean" things are always better than (whatever the alternative is), right? So therefore a product with a name that contains "cleaner" must be good. And it must be necessary, or hundreds of millions of IQ 140 people worldwide (did you know that almost no one has a lower than average IQ?) wouldn't use it. Those people are too smart to be duped by hype, right? CCleaner does seem to be the most highly regarded of the lot of them. If I ever find a need for it maybe I'll look it over. Installed Windows 95 ONCE and used it for years.Installed Windows 98 ONCE and used it for years.Installed Windows 2000 ONCE and used it for years.Installed XP x64 ONCE and used it for years.Installed Vista x64 ONCE and used it for years (that machine JUST burned out with bad caps, after 8 years running 24/7).Installed Windows 7 x64 ONCE and used it for years.Installed Windows 8.1 x64 ONCE and used it for a year so far. Tell me again what needs to be cleaner? -Noel

You seem to like to dig up documentation that supports things obvious to even a casual observer. Good on you. Imagine the outrage if the government were to overtly put a price on a human life - which is what a study to determine how much to spend on counter-terrorism of course produces. Since "terrorism" is such a hot button subject, maybe someone should accuse Microsoft of "cyber terrorism" for *****ing up Windows so badly. Yes, I think it's time for the government to get involved. That'll fix it. -Noel

Apparently it's possible to bring back mouse wheel routing to inactive windows being hovered-over: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Control Panel\Desktop] "MouseWheelRouting"=dword:00000003 Not my discovery; I saw it here: https://social.technet.microsoft.com/Forums/en-US/9094baec-2a9d-40f5-ae9b-e4acdd3c3bec/scrolling-windows-without-click?forum=WinPreview2014General#8c50ca0c-eb80-46c4-a147-fab4748d9dc0 -Noel

It's almost too sad and alarming to be joked about. Anything can be pulled over on the public in the name of security. Anything. After all more security is better, and much more is much better, right? Say, for example, Microsoft might want to make Windows 7 less and less attractive to use. They could roll out "security" updates where every byte of every file written and read would be lovingly examined by the OS every time it's accessed to make absolutely sure no malware is being introduced. Then, amazingly, because of "architectural differences", Windows 10 could be much, much faster, because it doesn't "need" such work at the low level. I suspect the only things preventing them from pulling this off is that 1) there ARE actually people smart enough to detect them adding unnecessary overhead, and 2) Microsoft is NOT actually smart enough to pull it off. -Noel

Thanks, BigMuscle. I'd certainly like to be able to change the inactive color to darken it some, but it's not unacceptable as is. Since it can't be set to a dark color, note how the inactive Win 10 window border whites out against a light background. Could you not just make it follow the setting in the registry to give people the opportunity to configure it as they see fit, even if the transparency can't be adjusted separately? -Noel

Works nicely on Win 10 6.4.9860.Works nicely on Win 8.1 6.3.9600The only thing I saw was that on my 8.1 test system, Aero Glass had been coming up without the nag dialog before, but the new version failed to load license.key (which I'd had on there since early in your Aero Glass development). Apparently your software now ONLY uses donation.key (I remember you saying you'd change it to do that). Easily solved by renaming the file. I'm not able to make the window borders on Win 10 inactive windows as dark/transparent as I've done on Win 8.1. This is not a new issue with this version. You said there was some limitation with the Win 10 version, right? I take it you've not been able to work around it? Not a big deal; inactive windows are just gray (on a dark background) instead of black. -Noel

Resources have shifted slightly. A theme atlas for Aero Glass beta testers of Win 10 build 9860... http://Noel.ProDigitalSoftware.com/ForumPosts/Win10/FauxBordersRoundedCorners.png -Noel

I *finally* just got a complete symbols download. Did you notice that the drop shadow isn't animated with the window itself? I think only 12 year olds (with their lifelong software development experience) must be working on the Windows UI now. Anyone here remember industrial "quick on" CRTs, which bloom a bit large first then settle? And shrink when turned off? Remind you of any build you know? Jarring indeed. -Noel Edit: I forgot to mention that a good portion of the top part of the INSIDE of the title bar is the resize region, while it's OUTSIDE the rest of the borderless window. Accidentally resize a window instead of moving it, anyone? Microsoft is deliberately trying to get us to hate the desktop.