Recommended Posts

  • 2 weeks later...
  • 3 weeks later...

bug: screencapturing the window itself (via alt+prntscrn) reveals that the window margin for the top bar is somewhat off. I havent looked into what it could be, but what I believe is happening is that youve set a few rows of pixels on the top to be transparent, instead of changing the margin of the top bar. Anyways, here's a screenshot (look at the top of the window):

post-80392-1121923605.png

bug: screencapturing the window itself (via alt+prntscrn) reveals that the window margin for the top bar is somewhat off. I havent looked into what it could be, but what I believe is happening is that youve set a few rows of pixels on the top to be transparent, instead of changing the margin of the top bar. Anyways, here's a screenshot (look at the top of the window):

586245972[/snapback]

Yep, it's the same bug as in Watercolor Lite 2.1.1, see here.

The author of the VS doesn't seem to be interested in fixing bugs anymore... :(

Im using Windows Extra Large fonts. There is a minor issue with it.

With the Luna theme on normal size fonts the title bar is one size. With every increased font size comes a wider title bar (and consequently, bigger minimize/maximize/close buttons) to accomodate the larger text.

Im not sure if this is related to using Extra large fonts, but the top of the window doesnt seem to want to give me the mouse cursor to expand the window. Its only on the top side of the window. The other 3 sides are fine.

AIM 5.9.3828 seems to have some issues.

I dont tihnk binary works on themes anymore

586260847[/snapback]

Not msstyles anyways. I still update Watercolor for Windowblinds internally, and I have a couple other skins near completion, but they require features that wont be out till Windowblinds 5.

As for the titlebar bug, it was the only way to stop the mozaic in the titlebar from stretching. If someone now has a fix for that I'd be happy to install stylebuilder and fix it. But I'd highly recommend people switch to using my WB version as it's more complete, usable and virtually bug free.

Chris

where can I get the latest Watercolor for WB? Is v2.5 the latest?

586271999[/snapback]

http://www.wincustomize.com/ViewSkin.aspx?...178&LibID=1&u=0

...But I'd highly recommend people switch to using my WB version as it's more complete, usable and virtually bug free.

But it's not free... :/

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

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!