Watercolor Emico

By Jamushroom
in Tips, Tweaks & Customization

 Share

Recommended Posts

Rising Star

Tweaker

Posted
Posted
I think it has something to do with the separators for the start panel menu's. The ones that you see when you hover over, as an example, "All Programs".

That wasn't it either. Although the font there were both black and I was able to change the muse over to white but it didn/t help the other menus from both showing up black.

I think it has something to do with the separators for the start panel menu's. The ones that you see when you hover over, as an example, "All Programs".

That wasn't it either. Although the font there were both black and I was able to change the muse over to white but it didn/t help the other menus from both showing up black.

post-3332-1214159362_thumb.jpg

Grand Master

Jamushroom Veteran

Posted
  • Author
  • Veteran
Posted

I meant the "All Program" menu from XP, it has a skinned menu which is being used in the menus from Firefox in Vista. Also, those shutdown buttons need to be skinned as well.

Rising Star

Tweaker

Posted
Posted
I meant the "All Program" menu from XP, it has a skinned menu which is being used in the menus from Firefox in Vista. Also, those shutdown buttons need to be skinned as well.

I'm not at home right now so I can't check it out in XP now. My laptop only has Vista. I'll see about porting in your shutdown buttons.

Rising Star

Tweaker

Posted
Posted
I'm not at home right now so I can't check it out in XP now. My laptop only has Vista. I'll see about porting in your shutdown buttons.

Those Shutdown buttons are another Vista bug. Here's the screenshot of them in Skinstudio but obviously they aren't render that way in the finished WB as the previous shot showed.

post-3332-1214161010_thumb.jpg

Grand Master

Jamushroom Veteran

Posted
  • Author
  • Veteran
Posted

That's weird :s There has to be a way to have them skinned, because I've seen Vista WB skins that had their own buttons there. Sorry, but I cant allow permission for a WB skin if those aren't skinned on Vista.

Collaborator

StarLion

Posted
Posted
That's weird :s There has to be a way to have them skinned, because I've seen Vista WB skins that had their own buttons there. Sorry, but I cant allow permission for a WB skin if those aren't skinned on Vista.

If I remember correctly, those can't be changed with a visual style, you have to resource-edit the system DLL containing the images.

You can still release the skin, but you'll have to package it with a pre-modified DLL file so the user can swap it out.

Rising Star

Tweaker

Posted
Posted
That's weird :s There has to be a way to have them skinned, because I've seen Vista WB skins that had their own buttons there. Sorry, but I cant allow permission for a WB skin if those aren't skinned on Vista.

No problem! I just went and looked at some of the VS for Vista and all of the Shutdown buttons are render the same way. Another reason why I like XP better. :)

Rising Star

tmr250z

Posted
Posted
@tmr250z: I can't add more substyles to this theme. Well I can but I'm not going to because then all the other subtyles should also have the toolbar option. I'll think about the black toolbar buttons. I've tried them already but IMO they should have a color. I'll ask my beta testers.

That's ok, lol, now that I am using the blue toolbar buttons on WE Black, I'm really starting to prefer them over the black ones. :D

Collaborator

StarLion

Posted
Posted
@StarLion: Then how does VStyler do it with all of his WB skins?

Oh, you were talking about WindowBlinds skins! Sorry, I thought we were talking about native Windows Vista MSStyles (where a resource edit is the only way to acomplish the change).

WindowBlinds can do it all on its own :)

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Nick H. · Posted

      I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • Halo: Campaign Evolved is out next month with new prequel missions

      By +pmrd · Posted

      As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Malisk · Posted

      I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • Microsoft confirms a new, useful Teams' app is coming very soon

      By Malisk · Posted

      I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame

      By hellowalkman · Posted

      Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.

  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!