MS Modifies black maximized borders


Recommended Posts

nice... gotta dl RC2 and judge on my own.. it looks a bit too dark.. but 10000x better than the black :)

His point was that this isn't going to be the only feature people complain about or love. In the end, the entire way the OS works has to be a compromise. Whether it's the color of a window or the way files are indexed, it's all a compromise. If MS were to give people what they want, there'd be 3 options for the transparency and then two or three for every other little nit pick aspect to the OS.

Completely understandable... but judging from what i've seen on LOTS of forums, I think this is one of their biggest problems. And obviously it is, if they've taken the initiative to change it.. and make it KNOWN that they've changed it.

It's not just that people will see through the transparency--the primary idea here was to use the letterbox effect to draw people's eyes to the content.

Ughh. I'm so sick of people using MS's canned response: "trying to draw peoples' eyes to the window content." The window is maximized!!!! Where the hell else would your eyes be instead of on the content of the window!!!!!!!!

Ughh. I'm so sick of people using MS's canned response: "trying to draw peoples' eyes to the window content." The window is maximized!!!! Where the hell else would your eyes be instead of on the content of the window!!!!!!!!

that's how i feel. Maximized windows have been working damned fine since Win3.1... I don't understand why the need to change it now after fourteen years.

Whata? anyone got a picture of this? I never took notice to it.

It is barely noticeable, unless dragging. Open WMP11 over a white background. Now drag the corners until you can't make wmp11 smaller. Now drag wmp11 across the screen. You should see stripes across the player "moving".

Long thanks for the screenshots, that's much better than the plain black, however I would be happier if MS would just let us pick exactly which color we want or better yet, let us select if we want transparency on the maximize windows or not. Still this is much better IMHO.

that's how i feel. Maximized windows have been working damned fine since Win3.1... I don't understand why the need to change it now after fourteen years.

That is the problem. Microsoft needs to forget the past and move forward. How much smaller would Vista be if MS started fresh with no backwards compatability.

Adding three options (Turn black (or a selected color), Turn off transparency, or Do Nothing) I think would pretty much fit everyone's needs. That isn't willy-nilly, or a million different options. I can guarantee if nothing was done, when Vista was released and people began using it, MS would get plenty of calls asking why their window is changing to black when they set it to Red, or orange, or green, or pink. Taking 2 years to internationalize three options? That shouldn't happen... But yeah... it is Vista, so I wouldn't be surprised.

Yes, I read the blog post, and if you check the topic in the shell revealed forums, I have posted there too. I know what the purpose of turning the window black was. I don't care what the purpose was. I have my Aero set to Reddish color. I DO NOT want them black. I want Aero the color I picked, not Microsoft. Maximized windows have worked fine since 3.1, why do they need to introduce this "letter box" bull**** 14 years later?

For points 3 and 5... XP was released 5 years ago, they "supposedly" began working on Vista before that. However, to me, it seems like they sat around with their thumbs up their asses until Beta 2 was released in MAY of 2006. Beta 2 was such a debacle they needed to get as much feedback as possible, and that's when they started to actually begin really working on Vista. That's what I meant... I guess it was kind of confusing :blush:

And as for the fade/animation type thing... I think that the window could be able to have a quick maximize animation... then after it was completely maximized, it could have a nice soothing fade to the black, or whatever color it is being faded to.

And your P.S. that's been complained about too. :) Don't worry, the MS teams knows all about it. :p

I'm not going to even bother arguing with you on the other points, because you seem to think you're the only expert on HCI and software design around here. Did we take too long to work on Vista? Yes. Was it because we just sat around drinking free soft drinks until B2 came out? No.

Vista was not exactly a number one example of how to manage a software project. No one is going to debate that point. By one analogy I have heard, working on Vista was like trying to change all four wheels on the car... while you're going 60 mph on the highway.

Basically what happened is Avalon was still being developed when the shell team decided to rewrite the shell to use Avalon. The shell is by no means a trivial piece of software. Unfortunately, since Avalon was still in development, it was bound to change. And guess what? It did. The framework changed halfway through. Guess what the shell team had to do? Yep, rewrite all of shell to work with the new Avalon. There's a lot more to this story, but that's the short version.

I'm not going to even bother arguing with you on the other points, because you seem to think you're the only expert on HCI and software design around here. Did we take too long to work on Vista? Yes. Was it because we just sat around drinking free soft drinks until B2 came out? No.

Vista was not exactly a number one example of how to manage a software project. No one is going to debate that point. By one analogy I have heard, working on Vista was like trying to change all four wheels on the car... while you're going 60 mph on the highway.

Basically what happened is Avalon was still being developed when the shell team decided to rewrite the shell to use Avalon. The shell is by no means a trivial piece of software. Unfortunately, since Avalon was still in development, it was bound to change. And guess what? It did. The framework changed halfway through. Guess what the shell team had to do? Yep, rewrite all of shell to work with the new Avalon. There's a lot more to this story, but that's the short version.

I think you just proved my point. Microsoft dropped the ball on Vista, and there are no excuses - well... aside from "it wasn't a priority, no budget, ran out of time".

I think you just proved my point. Microsoft dropped the ball on Vista, and there are no excuses - well... aside from "it wasn't a priority, no budget, ran out of time".

Hey, that's exactly what I didn't say. Good paraphrase! But hey, you're the expert here on software development. :rolleyes:

Hey why don't you whiny little neowhiners get a job at Microsoft?!?!?!

You are all obviously interface experts and surely could design a UI that every single living human being would instantly fall in love with. It's apparently very easy to do, but most of us don't have that 6th sense as you neowhining brats. So please use your infinite knowledge and vision to provide the world with the UI that it needs for world peace.

Thanks guys you rule.

Hey why don't you whiny little neowhiners get a job at Microsoft?!?!?!

You are all obviously interface experts and surely could design a UI that every single living human being would instantly fall in love with. It's apparently very easy to do, but most of us don't have that 6th sense as you neowhining brats. So please use your infinite knowledge and vision to provide the world with the UI that it needs for world peace.

Thanks guys you rule.

...........

Its not a design issue, its a basic "Allow Maxed windows to be transparent" opinion. Other than that I think the Vista UI isn't that bad.

...........

Its not a design issue, its a basic "Allow Maxed windows to be transparent" opinion. Other than that I think the Vista UI isn't that bad.

they might not be able to design a better interface, but there's way more people disliking the new UI compared to those who like it. so obviously there is an issue, i dont remember people complaining about XP this much.

What you people haven't even noticed is that all of the "Maximized Color" is changes is just to bring up the hype in yall. The relatively tiny "small" ammount of color they have added to the maximized windows has been there since Build 5600, and it has been tuned up about 4+ more on build 5728, if any; It does NOT show when you use the standard color (that is what they said now at the shell website), but it does show "a little bit more" if you switch to other colors like Frost, Blue, Orange, Pink, etc.

Now whether they are coming up with something really relevant to this if they get to release the pre-RTM build by tomorrow, that is something I do not know. But I am sure these news, aren't that much of a discoverage. What is it that you do when you get the beta builds? Test it? How?.... I see a lot of people who seems to be Beta testers to be asking for these stuff everyday when they're in front of their faces... :huh:

Look:

Default-max.PNG

this would be the Default color scheme Maximized.

Now these are the other color schemes available, each one maximized:

Blue-max.PNG

Blue Maximized.

Fros-max.PNG

Frost Maximized.

Graphite-max.PNG

Graphite Maximized.

Orange-max.PNG

Orange Maximized.

Pink-max.PNG

Pink Maximized.

Red-max.PNG

Red Maximized.

Teal-max.PNG

Teal Maximized (my favorite).

Tip:

You can appreciate the color change in the PNGs better if you are using a TrueBright CrystalClear Display, like those in VAIO LCDs or HP Compaqs V2000 and up; I've noticed that it depends on your display; so for some people it might look black if your brightness is too low or under 50%, contrast, etc...

Also this is what I was reffering to in a thread which I forgot to reply back to whoever asked me how; there you go my friend...

I liked the letterboxed look. Hmm, oh well.

You can apparently still keep the same sort of look prior to these changes if you retain the default colour settings. I've read that a couple of times both here and at shell: revealed. No stress! :)

aside from the issue from whether they should have changed it or not..

i really really find it weird people are saying 'i dont like black; i want it the color i want, etc'. black is a basic color, like white. its not like they're forcing you to make it hot pink, forest green, or bright orange. when things are black, it does not make it look goth. its a basic color, ok--black, white, gray. when you used DOS, the background was always black. ok, its just really weird.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!