Recommended Posts

I don't think that's broken. I think it's scrolling panel and the partial box on the left is another date in the file history.

That's exactly right, the box is the view of the folder with the date at the top, hit the back arrow and you get the next box to the left with older versions.

The blue is the default color scheme. However, you can change it. Microsoft cancelled the project to have white window boarder and a taskbar color independent to the boarders. The default is the blue you see, with the background image being the flower. The color of the boarder and taskbar will adapt to the background you pic or, if you choose, can be set to a custom color.

I'm laughing my ass off all the Windows Vista & 7 styled system icons are still there? Must sting for all those fanboys who kept claiming Microsoft would adopt a new Metro-styled set in the final version to at least partially fix the inconsistent Desktop/Metro mess. It's amazing how Microsoft managed to make the Office 2013 icons look awkward just about everywhere: They clash with Windows 7, they clash with Windows 8's dated desktop icon set - which in turn clashes with new Desktop theme - and they look weird in the Start Screen. Seriously, what a joke! :laugh:

Also, do the Windows and Office team not know how to reach each other to synchronize their interface planning efforts? Apparently each devision was given instructions to somehow apply some sort of Metro look to their respective products. Further communication and overview ceased there.

This is just final proof: Micrsoft's Windows team doesn't know what words like "consistency" and "detail" mean and the company doesn't care about providing a polished experience at all when it comes to their desktop OS. I absolutely love Metro on my Nokia Lumia 900, but what they did to Windows 8 is just bad.

I agree with many that the old aero icons need to go. They stand out and look out of place with the new flat theme. Come on Microsoft, is it really that hard to change them? They can even use Office's icons for the explorer ribbon. At this stage I doubt they will change the icons. It seems with every release of Windows there's something always missing. Vista was the only one that changed mostly everything and felt consistent for the most part.

What I think is the worst thing is how there is no visual depth at all. When you're working with Windows that can overlap you need to have some visual cues of what is on top of what. Just a very subtle shadow (doesn't have to be as huge as it is in OSX/Vista/7) would suffice for this.

I have mixed feelings about the consistency of icons. While it might be nice to have Metro icons across the board the reality is that it's going to take years before even a majority of desktop apps come with a Metro-style icon so there's always going to be a mixture of styles. Sure, MS could lead by example but there will always be 3rd-party developers that don't update their icons, often because the same apps will be run on earlier versions of Windows where a Metro-style icon doesn't make as much sense.

For now, I think the non-Metro icons make it clear which apps run on the desktop and which don't.

I also don't like that I can no longer change the fonts used throughout the Desktop and elsewhere. I can alter the size, but not the actual font. No idea why they took away such basic functionality that has existed since... Windows 1.01?

I've been scrutinizing the Windows 7 Aero theme lately; the rounded corners have been bugging me, as well as the gradients in the title, window boarders and task bar. The new flatter, solid color Windows 8 themes do indeed seem to make the Windows experience nicer looking, except I think they should not have remove transparencies.

I've been scrutinizing the Windows 7 Aero theme lately; the rounded corners have been bugging me, as well as the gradients in the title, window boarders and task bar. The new flatter, solid color Windows 8 themes do indeed seem to make the Windows experience nicer looking, except I think they should not have remove transparencies.

I'm not so sure. Transparencies can go, but you need shadows to achieve a feeling of depth. No shadows = too flat.

That's one of the problems I still see with Metro. On their 'digital authenticity' crusade Microsoft are actually removing (or aren't considering to include) all kinds of visual clues that help a human quickly understand an interface. Metro supposedly has its origins in print design. But that isn't interactive. It's just the presentation of information. So the question of usability doesn't even come into play, just how well the information can be absorbed?!

post-5569-0-37126800-1343081269.jpg

I certainly don't like the consistency issues, though, as have been pointed out: Office and Windows using different borders and Win8 still using old Vista-era icons that are not "Metro" in any way.

Yeah, more consistency would be better. Particularly I'd like Office's default behaviour when typing to disable the mouse cursor would be a really welcome addition to Windows for all text input boxes.

I also don't like that I can no longer change the fonts used throughout the Desktop and elsewhere. I can alter the size, but not the actual font. No idea why they took away such basic functionality that has existed since... Windows 1.01?

I imagine that'll slowly get added back in. They're working on the most important stuff to start (not that fonts are unimportant, but as far as hierarchy goes...), and building up the functionality there. That's better than having all the legacy code sticking around messing things up. Probably also why they're not worrying too much about the icons and are instead focusing on building the Metro UI.

I'm not so sure. Transparencies can go, but you need shadows to achieve a feeling of depth. No shadows = too flat.

Wait a second, I thought the windows did still have shadows, but AFAIK it's only the active window, I'll have to ask about this, because if there's no shadow then that's a serious usability issue like has been mentioned.

Yeah, more consistency would be better. Particularly I'd like Office's default behaviour when typing to disable the mouse cursor would be a really welcome addition to Windows for all text input boxes.

You can disable the mouse cursor while typing since a while. Go inside the "mouse" option menu and look for it.

I have to wonder with the screen shots of win 8 rtm and office 2013 whitewashing everything...is Microsoft going the primary path of download only and cutting back on retail versions of windows? think about it the blah screen shots of win 8 and office would be easier to download because it cuts back on code....Thoughts?

I have to wonder with the screen shots of win 8 rtm and office 2013 whitewashing everything...is Microsoft going the primary path of download only and cutting back on retail versions of windows? think about it the blah screen shots of win 8 and office would be easier to download because it cuts back on code....Thoughts?

I expect they will still offer retail disks, but it makes sense for them to push the digital downloads, it cuts back on costs and allows the user to download the product from the convenience of their own home.

They can even use Office's icons for the explorer ribbon.

That means the Office and Windows teams would actually have to plan things with one another. Which apparently is asking for the impossible this past decade.

  • Like 2
That means the Office and Windows teams would actually have to plan things with one another. Which apparently is asking for the impossible this past decade.

forever actually not just last decade :p

That means the Office and Windows teams would actually have to plan things with one another. Which apparently is asking for the impossible this past decade.

That. I really, really don't get why teams within Microsoft can't work together. None of their software products has ever had any sort of coherence with the others. Office, Windows, Windows Live/MSN, Zune, Xbox, ... Lately they have been sharing some Metro ideas (really just the huge light Segoe/Zegoe) but it still all looks completely different. Even Office 2013 doesn't fit into Windows 8 properly. It gets close, but it's just not as it should be.

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

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!