Re: [ddraw] asynchronous screen updates

2004-02-05 Thread Ove Kaaven
ons, 04.02.2004 kl. 23.31 skrev Lionel Ulmer: > > Then I would be drawing rectangles which are not ready for a redraw yet. Does > > UnLock release only last lock or all locks on these old DX versions? > > Well, you need to store the rectangle at Lock time but only draw it at > Unlock time. And I

Re: [ddraw] asynchronous screen updates

2004-02-05 Thread Piotr Pawłow
On Wednesday 04 February 2004 23:31, Lionel Ulmer wrote: > Well, you need to store the rectangle at Lock time but only draw it at > Unlock time. And I have no idea if any game ever does concurrent locks (so > I have no idea how concurrent lock work). OK, so that is another thing to find out > So

Re: [ddraw] asynchronous screen updates

2004-02-04 Thread Lionel Ulmer
> Then I would be drawing rectangles which are not ready for a redraw yet. Does > UnLock release only last lock or all locks on these old DX versions? Well, you need to store the rectangle at Lock time but only draw it at Unlock time. And I have no idea if any game ever does concurrent locks (so

Re: [ddraw] asynchronous screen updates

2004-02-01 Thread Piotr Pawłow
On Monday 26 January 2004 22:44, Lionel Ulmer wrote: > The only comment I have on the patch is that you are using the rectangle > from the 'User_DirectDrawSurface_unlock_update' code. The big problem here > is that for old DirectX versions (versions 1 to 3), the lock rectangle was > not repeated in

Re: [ddraw] asynchronous screen updates

2004-01-26 Thread Lionel Ulmer
> Here are my changes: > > - User_add_dirty_rect is now an asynchronous equivalent of > User_copy_to_screen. It adds the rectangle to the list of dirty rectangles > and signal the update thread that there is some work to do. > - update thread calls User_get_dirty_rect to iterate over the list of

Re: [ddraw] asynchronous screen updates

2004-01-21 Thread Piotr Pawłow
On Wednesday 21 January 2004 12:53, Mike Hearn wrote: > Metacity is normally a good barometer of whether we got WM stuff correct. > What errors do you see exactly? Are we created unmanaged windows here, or > are they managed but with screwed up NETWM attributes? Metacity displays two messages: #

Re: [ddraw] asynchronous screen updates

2004-01-21 Thread Mike Hearn
On Wed, 21 Jan 2004 06:36:09 +0100, Piotr Pawlow wrote: > windows managers (kwin > cannot raise the window, metacity complains that the window attributes do not > make sense). Metacity is normally a good barometer of whether we got WM stuff correct. What errors do you see exactly? Are we created

[ddraw] asynchronous screen updates

2004-01-20 Thread Piotr Pawlow
If DGA is not available, Wine falls back to creating offscreen primary surface and blitting all changes to the screen. It knows which part of the surface might have changed by watching unlock calls. However, as Jukka Heinonen pointed out in his message posted on 17.10.2001, the update logic in