• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About inighthawki

Profile Information

  • OS
    none specified
  • Country
  1. Noel, the reason was not about battery (I dont think they ever claimed that either). It was due to performance on low end tablet devices.
  2. It doesn't automatically determine if Aero Glass is installed, you have to turn on the option "Enable Aero Glass" from the Menu Look tab. When that is on, it just skips the hack that converts the opacity from "glass" and "fullglass" to "alpha" and "fullalpha". So the Start menu renders glass like on Windows 7. Ah, awesome thanks. I was looking at the options under "Skin"
  3. May I ask how ClassicShell 4 determines if bigmuscle's aero glass is installed?
  4. Okay and for the picture bigmuscle ? How to disable this message? and.. the control box I found a way temporarily to close it.. if you have a suggestion to close it at each startup. It cannot be disabled, that is the point. He explicitly states that this is a beta/prototype build and not intended for normal use.
  5. Wow, I didn't notice that before. We are left to wonder why Microsoft would put effort into making such a change. More of their gradual "weaning" away from allowing users to customize the UI at all? When does that ridiculousness end? When there's one and only one UI look and feel, I guess. Definitely goes against everything BigMuscle is doing. -Noel Yeah there couldn't possibly be a good reason, perhaps mathematical, to clamp a value to these numbers. Clearly they solely wanted to limit the user experience to 75% of the color intensity range for no reason.
  6. People keep aying things like that, but Microsoft doesn't go and add stuff just to piss off 3rd party developers and try to disable circumventing of third party themes. What would they gain? The reason is almost certainly just a theming bug that isn't caught because Microsoft only ships a single theme. Since they do not officially support third party theme modding, they likely don't have any kind of tests that would ensure things like that work. More importantly, you have no proof to back up your claim, so why form these irrational justifications just so someone passing by on the forum sees it and then spreads it as a rumor, what does that solve?
  7. Clearly Microsoft doesn't want this to work. In their twisted minds, they want to close off everything, so that you get what they give and nothing more. lol, are you for real? Do you think the people at Microsoft have some master plan to control how you use your OS or something? The "restrictive" stuff that they put in Windows is for the concern of security and nothing more. I hope you're not one of those conspiracy theorists who believe that everytime a windows update breaks some hack it's because Microsoft purposely put in some way to prevent it.
  8. Release Preview Theme Is it? It appears to have the window frames of he RP theme yet the taskbar of the RTM theme...
  9. I'm impressed, that was very quick work (buggy or not) . Nice job.
  10. No, please read my post a couple up.
  11. Just to clarify a few things about the text. The solid blocks of color you see is NOT the text glow. It is a DWM optimization to improve font rendering performance by no longer alpha blending the text with the frame. It is instead rendered into an opaque texture of the same color as the theme color. I personally don't like this idea because it reduces the personalization capabilities of users with modded themes, since the background color of the winow now must exactly match the color of the theme as a solid block of color to work. I have no doubt that bigmuscle will work around this and maybe render font differently though. The reason the "glass" window does not have this is because the ribbon UI renders its own non-client area. The text glow will also not work on the windows with the new text rendering (I cant say about the ribbon windows, though)
  12. bigmuscles utility (as it stands) will not work on 8.1 at all, and has nothing to do with the high contrast. It is because unlike in Win8, 8.1 actually stripped out all references to the glass code. The blurring and utility functions to make it function are nonexistent.
  13. Maybe, that is the cause: http://support.micro...b/2850674/en-us? Interesting. So some unlucky people might have their computer rendered unbootable by no fault of their own, and there is no fix? (except, of course, a backup image on a whole separate hard drive, which everyone has) Were there patched theme files in play here? If Microsoft updates components that touch any patched files, it may only be able to load digitally signed files (themes) and thus DWM will fail to properly initialize without theme data. It occurred with a windows update that happened a while back, I imagine it could theoretically happen again...