Recommended Posts

I think his point was that OpenOffice can do most of what Office 2007, for infinitely less price wise. For opening documents, it'll do just fine. For hardcore business people who make documents for a living, Office 2007 would be much better, but it's a few hundred dollars more than OOo.

yes i really digg openoffice 3 over office 2007. it's faster, does pretty much everything and it's free. office 2007 seemed pretty slow to me.

You're dead on right.

The good news is DirectWrite will solve this and finally bring great Asian font rendering to Windows. (see the demos in Neowin's PDC coverage for examples, or pop on the Engineering Windows 7 blog)

The bad news is almost 90% of today's apps which use GDI will still continue to have crappy arse fonts. :/

Even on Linux, the font rendering is a bit sketchy for Western fonts, but Asian fonts look damn good.

(side note: I can't write in Chinese, though that's my background. But there's a handful of people on my contact list who do use Asian fonts, and they look ugly.)

edit: Here's an example. Take a look at the font rendering on the icon's previews.

post-99705-1228871807_thumb.jpg

That is how it should look all the time, is there a timeframe on Directwrite? I'd assume it'll take quite some time to implement into Windows?

The good news is DirectWrite will solve this and finally bring great Asian font rendering to Windows. (see the demos in Neowin's PDC coverage for examples, or pop on the Engineering Windows 7 blog)

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Because not everybody can or wants to write managed code.

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Full screen zoom in Windows 7 gives pixellated output even for WPF apps. I hope they'll consider adding in a billinear filter to make the zoom as smooth as those found on OS X/Compiz Fusion.

yes i really digg openoffice 3 over office 2007. it's faster, does pretty much everything and it's free. office 2007 seemed pretty slow to me.

Problem with Office 2007 is MS attempt to do everything with it. When you create email message it gets created in html format. For simple text you get such crappy html code...pages of crap ms puts in there.

Here's something I personally would love to see done with WMP12 - make the mousewheel functional. Right now, in almost all other media players (Media Player Classic/Home Cinema, VLC, etc) scrolling the mousewheel changes the volume, which might not seem like a big thing to a lot of people, but it's so tremendously useful sometimes. Instead of giving an app focus and then having to go cursor to volume control, you'd save the last step just giving the app focus and rolling the wheel up or down as required.

Yes, I do have a keyboard with volume controls on it, but but but... the mousewheel is there for a reason, and other media players put it to very good use, so why not WMP this time out...?

Heres something that I would love to see implemented.

The "BRAND" New UAC Dialog.

When you launch a new program, that needs privileges, there is a tick box saying []Would you like to save this configuration

If you tick it, and press yes then it always launches in Elevated under the .exe . BUT. I know your thinking, viruses could manipulate this program and make it so it launches the virus code.

If microsoft implemented some kind of check (etc. MD5) every time it ran, if it matched the original dialogs MD5 then it will run without the prompt and if it doesnt then it will launch the UAC prompt. It also needs to be in the exact place for it to pass.

Heres something that I would love to see implemented.

The "BRAND" New UAC Dialog.

When you launch a new program, that needs privileges, there is a tick box saying []Would you like to save this configuration

If you tick it, and press yes then it always launches in Elevated under the .exe . BUT. I know your thinking, viruses could manipulate this program and make it so it launches the virus code.

If microsoft implemented some kind of check (etc. MD5) every time it ran, if it matched the original dialogs MD5 then it will run without the prompt and if it doesnt then it will launch the UAC prompt. It also needs to be in the exact place for it to pass.

As bulletproof as that sounds, it wouldn't be that hard to get past those security measures.. MD5's can be faked fairly easily.

Is it just me, or does the Start Button look completely unimportant?

It doesn't look completely unimportant, but I sort of agree. In terms of appearance, the Start button has been pushed a bit into the background, starting with Vista, and now Windows 7.

I like how it looks in Vista. It's not as prominent as it used to be with the huge word, "Start", but how it sort of sticks out a little bit over the taskbar makes sure it isn't completely lost.

For new computer users, it's definitely less discoverable, since there's no longer a completely obvious place to, "Start" using the computer, and this is probably going to carry over into Windows 7 as well, but I think it isn't any harder to become familiar with than any other interface.

Here's something I personally would love to see done with WMP12 - make the mousewheel functional. Right now, in almost all other media players (Media Player Classic/Home Cinema, VLC, etc) scrolling the mousewheel changes the volume, which might not seem like a big thing to a lot of people, but it's so tremendously useful sometimes. Instead of giving an app focus and then having to go cursor to volume control, you'd save the last step just giving the app focus and rolling the wheel up or down as required.

Yes, I do have a keyboard with volume controls on it, but but but... the mousewheel is there for a reason, and other media players put it to very good use, so why not WMP this time out...?

As opposed to how the mousewheel already is functionally used for scrolling the library?

You named two library-less players as comparison. "Scroll in view" is the default logic for what a scrollwheel does. If you somehow decided that the mousewheel should *not* activate those slider bars, you'd rightly leave people very confused about the noncohesive design.

It doesn't look completely unimportant, but I sort of agree. In terms of appearance, the Start button has been pushed a bit into the background, starting with Vista, and now Windows 7.

I like how it looks in Vista. It's not as prominent as it used to be with the huge word, "Start", but how it sort of sticks out a little bit over the taskbar makes sure it isn't completely lost.

For new computer users, it's definitely less discoverable, since there's no longer a completely obvious place to, "Start" using the computer, and this is probably going to carry over into Windows 7 as well, but I think it isn't any harder to become familiar with than any other interface.

When I say "completely unimportant" I mean in context with other Taskbar items. Everything has been made bigger and bolder, but the Start Orb has just been left. Nothing about it says "Click here to start" - the only visual clue that it's special comes when you hover over it, by which time it's already been clicked on. In Vista, it sticks out and has a kind of glass bubble look, but in Win7 it just looks dull (and squashed) compared to the rest of the Start Menu.

When I say "completely unimportant" I mean in context with other Taskbar items. Everything has been made bigger and bolder, but the Start Orb has just been left. Nothing about it says "Click here to start" - the only visual clue that it's special comes when you hover over it, by which time it's already been clicked on. In Vista, it sticks out and has a kind of glass bubble look, but in Win7 it just looks dull (and squashed) compared to the rest of the Start Menu.

The position of it, still indicates it's importance. Fitt's Law assures us of that.

However, with the this new taskbar and quick launch system, the importance of the start menu is decreased.

How so (I'm not arguing, but would actually like to know!)?

http://www.xvsxp.com/interface/fittslaw.php

Screen corners guarantee an 'infinite' target with almost no precision or dexterity required. Just move your mouse mindlessly in one direction and click.

Nope, you can't move the icons to the middle or far right of the task bar and lock them there. :)

You can if you fill the taskbar with icons, can't you? ;)

I know what you are saying though, it might make more sense to let us move the icons to the middle (or right) if we wanted. It would make the taskbar tidier to have the icons centre aligned, I reckon :)

Nope, you can't move the icons to the middle or far right of the task bar and lock them there. :)

Woops, that was a mistake. I meant that you can move icons into the taskbar, but, you're right, you can't lock them anywhere.

If the items were locked to the center of the taskbar, then in terms of appearance if really would be something like a dock. :laugh: .

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!