Recommended Posts

Pointers:

The titlebar is too bright while my taskbar isnt. Why not make them the same color?

screenqk7.jpg

The ability to only patch the taskbar and not the title bar and visaversa would be nice.

All in all great program! I hope to see future updates!

Pointers:

The titlebar is too bright while my taskbar isnt. Why not make them the same color?

The ability to only patch the taskbar and not the title bar and visaversa would be nice.

...

It seems that Microsoft has linked the transparency of the Titlebar to the transparency of the Taskbar. The msstyle patch modifies an internal resource of the patch, changing one alpha value. You might want to check out AeroXP.org, they create a lot of custom styles. Which you can use now, because your system is patched ;)

I just tried again and I'm getting the same error on x64

I see that I have a bit of work to do on the 64bit version. It's quite hard to tell if you are running 32bit or 64bit. I'll try to release an update in a few hours (when I'm at home). Unfortunatly I don't have a 64bit at home to test it on.

And i'll change the program logo to an image, I forgot that not everyone has the Chiller font :)

Thanks again all for testing.

I've created a new version 0.1.3

- 64bit detection should work now, and the files not found msg should be gone

- When the system or styles have state corrupt, "patch anyway" now really patches them

- 64bit/32bit mode detection happens before displaying a potential error (easier for debugging)

- Replaced the text logo with an image (Chiller font is no longer necessary)

- I disable the buttons after you press them to prevent double execution

64bit users, fire up your engines :)

Would a mod be so kind to remove the version number of the title of this topic? Thnx!

It seems that Microsoft has linked the transparency of the Titlebar to the transparency of the Taskbar. The msstyle patch modifies an internal resource of the patch, changing one alpha value. You might want to check out AeroXP.org, they create a lot of custom styles. Which you can use now, because your system is patched ;)

Well but that doesnt answer my question: Why is the titlebar brighter than the taskbar (or any other bar) and why can't you change it to be the same color?

This has already been done in this thread has it not?

The patches can be done manually, this thread is about a tool which does the patching process for you.

Well but that doesnt answer my question: Why is the titlebar brighter than the taskbar (or any other bar) and why can't you change it to be the same color?

Think of the msstyle as a big resource library (settings, images, version info etc.) that defines the look of your system. The msstyle patching part of VistaGlazz opens the Aero.msstyle, reads it's resources and changes one byte. That byte determines the opacity of both the titlebar and the taskbar (and start menu and more) when a window is maximized.

The default Aero msstyle defines that the taskbar is darker than the titlebar. My tool doesn't change that. If you have patched your system files, you can use any (unofficial) Vista msstyles/theme.

I suggest you try the theme that I've uploaded here (Aero MaxGlass LH by sonicexcess). He has modified the Aero msstyle slightly, and the taskbar is almost as transparent as the titlebar. I'm using it on my system right now.

Install is easy: just copy the content of the .rar file to C:\windows\resources\Themes and doubleclick the .theme file.

Everything tested now mate on Vista x64 and it works with absolutely no problems.

It detects it, patches system files. And does the theme.

If you need any more testing just PM me and I'll happily help

Thank you

Wow! I'm glad 0.1.3 fixes the problems.

At the end of next week I'm going on holidays (for two weeks), I hope to get a new website up for the tool and place it on things like Softpedia before then.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nothing is stopping you from continuing with your testing cadence. If updates are released every 2 weeks instead of 4, and you test once every 4 weeks, the exact same amount of patches will still be available for you in those 4 weeks. For example: Before 4th week - patch 1, 2, 3, 4 After 2nd week - patch 1 and 2 4th week - patch 3 and 4 Still the same amount after 4.
    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!