UCyborg

Member
  • Content count

    111
  • Joined

  • Last visited

Community Reputation

29 Excellent

1 Follower

About UCyborg

  • Birthday

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

510 profile views
  1. There is another type of glow effect besides the one from the atlas image, composited glow effect. If you find the theme where setting Caption glow effect mode to Use theme settings in Aero Glass GUI produces glow, you should be able to get same type of glow in Ribbon windows. I know for certain such themes exists for Windows 8.1 and 7. Composited glow effect is what you get out of the box on Windows 7.
  2. Compatibility modes only hook legacy GetVersion and GetVersionEx APIs, Firefox uses VerifyVersionInfo. There is a bunch of CSS stuff in there that adjust UI differently if ran on Windows 10. Supposedly whole capability for querying OS version using CSS was implemented so the UI can adjust according to the used OS. I'd really like to know where exactly Windows caches manifests. Because just saving the file with Resource Hacker didn't change anything. Only when the modified date changes on the .exe it will re-read the manifest. When you put back the original modified date, it will use original manifest.
  3. I removed Windows 10 GUID from firefox.exe's manifest with Resource Hacker, then altered firefox.exe's last modified date by opening it and saving it again with Notepad for Windows to register new manifest (Resource Hacker doesn't do it). Now it thinks it runs on Windows 8.1 and behaves just like it does on said OS.
  4. @NoelC Exactly, you only need it if you want glass at other places. And then the URL bar and search bar have greater heights, which is also Windows 10 only behavior. I use Firefox on Ubuntu occasionally, where I get the exact frame according to Window Decoration settings. It's only Windows 10 where it has to act differently.
  5. These should explain everything: I also like the default behavior on Windows 8.1 where glass is applied only on the title bar. GlassMyFox makes whole window glassy, which is not what I want. It also doesn't fix the standard 3 buttons hover-over effect. And if I want custom persona, I can only get those atrocious white buttons instead the ones from selected theme's .msstyles or atlas image override from Aero Glass on Windows 10. Everything is fine on Windows 8.1. One good thing comes out from using default aero.msstyles with custom persona on Windows 10, the standard 3 buttons blend with the persona.
  6. I just compared default settings under HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics between Windows 8.1 and 10. The only difference there is in a single byte in CaptionFont and SmCaptionFont settings. Applying Windows 8.1 settings gives larger font on 10. That is changing the first byte of said settings from F4 to F1.
  7. Firefox has these oddities only when ran on Windows 10. On older Windows versions, its default title bar has glass effect, along with standard 3 buttons straight from theme atlas image. If only there was a switch to turn off this Windows 10 mode.
  8. I just remembered about the quote from here: https://itvision.altervista.org/why-windows-10-sucks.html You're right though, if you love working on these things, you'll definitely want to perfect your code. About that bug that is triggered when new accent color must be taken from the new background, whatever kind of refresh in Explorer it causes, it's not the same as when you hit F5 key. This one puts the scrollbar back and isn't triggered if you're in the middle of renaming a file. There are some nice little things there and there; task view, new action center, ability to use mouse wheel to scroll in inactive windows. Did anyone notice new GUI for editing PATH environment variable? Other things just make no sense at all, eg. what was the point of removing GUI for editing and ordering WiFi connections? Windows 8 and 10 have to be the only OSes in existence where you can't access these settings in a normal fashion.
  9. True. They still haven't fixed this neither: https://answers.microsoft.com/en-us/windows/forum/windows_10-files/windows-10-file-explorer-scroll-bar-keeps-jumping/11c11063-569d-4b37-97ea-68a438b5dff4?auth=1 And judging by certain answers in that thread, they never will. Why bother when the user can just turn off bug provoking feature?
  10. Word 2016 has its own border and it's not a Metro app, but its borders surely look like those of Metro apps. It really depends on each individual application's customizability options. PotPlayer for example comes with 2 skins, default one has a custom border and the other one gives you the regular borders. If I understand correctly, Microsoft wanted to make all-in-one OS, so they force such design on all devices, supposedly so the same system appear consistent across various devices, which obviously doesn't make much sense. Phone and a full-blown desktop is like a night and day in many aspects. Windows Aero is Microsoft's full set of guidelines for UI design, which emerged with Windows Vista. The glass effect is rendered by Desktop Window Manager, responsible for rendering whole UI using graphics hardware acceleration since Vista. The functionality for rendering glass effect was removed starting with Windows 8. Aero Glass that we're discussing on these forums is an unofficial extension to DWM that adds glass functionality back. It was coded by Big Muscle alone AFAIK. Community here provides feedback. The appearance of window borders is influenced by theme atlas image (which is what this thread is about). This image can be overridden by Aero Glass. The way Windows theming engine works, this image is part of selected theme's .msstyles file. Custom themes that come with their own .msstyles have the most influence on Windows UI appearance.
  11. My experience with NVIDIA's drivers in general is that after some point, I just have to stop updating them because rather than improving something, they break things. I did read about that issue you mentioned, my problems with newer drivers are stuttering in games and stability issues. 368.81 is the last version that at least gets most things right, but I prefer 347.88 as it's the most solid in my experience. Luckily most games I play occasionally work fine with 347.88, but certain titles like DOOM (2016) require something newer to run optimally. Vulkan API also wasn't around when 347.88 was released. I also have a mouse for which exist some outdated custom driver, which likes to make PC BSOD. Had to prevent Windows Update from installing this one as well. The only thing I found useful about it is ability to set USB polling rate from its application, but universal Sweetlow mouse driver works well for that purpose. I just remembered switching the polling rate with the help of buggy driver I mentioned even crashed Windows 7 sometimes, but after the switch, there were no issues. There aren't any issues at all with Sweetlow driver. They shouldn't host buggy drivers on Windows Update, but since you have support for majority of graphics cards bundled in one driver package, that won't ever change in NVIDIA's camp unless they change their ways.
  12. The title bar height depends on type of window application creates, for example non-resizable window will have lower bar height than a resizable window. This is in their regular non-maximized state. For those familiar with Windows API, WS_THICKFRAME is the Window Style of interest. It's odd indeed, the height should be constant. Or add an option to tweak the behavior to one's liking. Is this supposed to be some sort of accessibility feature? Can't think of the good reason for the current behavior. Someone intentionally made it like this though.
  13. It's strange because I clearly remember graphics drivers were offered in the past if I had no driver, but they would disappear after I installed them on my own without Windows Update's help, regardless of version I installed. And AFAIK, the NVIDIA driver version 376.53 wasn't put on Windows Update servers yesterday, been up a bit longer, only yesterday they were automagically installed. And I wondered why my PC was acting funny after a trip to the bathroom! Thanks for the hint about the policy setting. Regarding default drivers' dates, never gave a lot of thought into that. Interesting blog post. That they wouldn't be touched at all since 2006 doesn't make much sense. But there is another similar convention. Check your CPU properties.
  14. @sierra117 Did you only try Firefox to come with that conclusion regarding title bar buttons? Firefox has custom title bar. On my end, title bar gets shrinked on every application with regular title bar and it is indeed the most noticeable when you look at title bar buttons. This is with default settings, messing with those registry settings will just have a more obvious effect. Note that Windows 7 eg. has the title bar height set the same as Windows 10, and yet the title bar buttons don't appear as big. Edit: Title bar shrinks on both Windows 7 and 8, title bar buttons are only affected as they are on Windows 10. Might be because they're so much larger compared to those on 7 and 8. So when the title bar shrinks, no space is left for the buttons so they must be shrinked. And registry settings affect everything in a relative way. At least that's what I see.