Will Windows XP (x64) fix desktop screen tearing bugs.

[xMax]

For this problem alone, which has annoyed the hell out of me, not to mention its implications that there could also be artifacts in media player, must have a fix. But i dont want to get into details, since some people dont have it and some people do, as figuring out why its happening on my system is too much of a headache for the moment. Instead, i will simply ask: "Does Windows XP x64 fix the deskotp and GDI screen tearing issues that occur on many computer systems?".

Vista apparently fixes this bug or issue, but it is not wise to get Vista as the primary operating system for professional or serious work.

 

[VirtualLarry]

I saw it mentioned in another thread on AT, that the reasoning behind it is that the GDI desktop is not double-buffered by the OS. Makes a certain amount of sense, really, although a double-buffered option would certainly make it look nicer.

For a similar example that you can experiment with, the Firefox browser double-buffers the display by default. You can change a pref to make it single-buffered, and then you can see a bit of the redraw/paint activity. (Set the paintdelay to 0 as well.)

Most VB/ActiveX controls that deal with bitmaps also double-buffer to prevent the controls from flickering.

So why doesn't MS do this with the desktop/GDI? Good question. Perhaps it has its origin in the relative lack of video memory for many cards during the early heydays of Windows.

 

[xMax]

So then that means that windows media player is probably double buffered, even though the GDI for the desktop is not. And that many applications 'sort' of override the GDI and use different rendering methods which could result in all sorts of different and advanced rendering, even when the GDI is only single buffered and poor in functioning for displaying images without flickering.

That makes sense. I also noticed that windows media player produces the same tearing(flickering) effect when the video mixing renderer is turned off but produces proper displaying of images, without tearing, when it is turned on. And this happens on my system because the legacy GDI takes over the displaying of my animations when VMR is turned off.

 

[smack Down]

First off all you posted this same retard thread before and still haven't said what VMR is.

Second double buffering doesn't really have much to do with screen tearing. Screen tearing happens when the screen is updated while it is beging refreshed so half the picture from the last fram and half from the new frame are displayed. Double buffering prevents flicker.

Thrid there is simplely no way to force any program using the current GDI API that doesn't impement double buffering to be double buffer with out changing the code. In fact any OS level double buffering would make the problem worses.

 

[xMax]

I dont recall anybody asking me what VMR is, which is the video mixing renderer in windows media player (10). And i dont know where you get off saying that double buffering has nothing to do with screen tearing when ive read countless reviews, discussions, tutorials, and other information that all mentions double buffering and tearing being related.

But anyhow, i need to work this sh** out in my head. Because i may be barking up the wrong tree.