
|
[haiku-appserver]
||
[Date Prev]
[10-2004 Date Index]
[Date Next]
||
[Thread Prev]
[10-2004 Thread Index]
[Thread Next]
[haiku-appserver] Re: drawing thread
- From: Adi Oanca <adioanca@xxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Mon, 25 Oct 2004 22:31:21 +0300
Rudolf,
I don't really see why that is useful. maybe you can explain more
clearly. Thanks.
Rudolf wrote:
> Hi,
>
> a small update on that 'other' doublebuffering:
>
>
>>Only good solution: double buffering entire screen and blit to
>>offscreen memory only, then switch offscreen onscreen during retrace,
>>then blit now onscreen memory to now offscreen buffer. Repeat when
>>needed. 8-)
>
> I would say make it triple buffering so things keep transparant to
> existing apps and BDirectWindow for example.
> 1. have a normal screen, that's never shown. Here everything is drawn
> into, so also by apps.
> 2. have the pageflipping doublebuffering in place, that gets its
> content from 1.
>
> Maybe I'll try to tweak the NV driver (outside CVS) at some point to
> see if I can manage to set this up as a proof of concept: I think, with
> some limitations, it might be possible. I should probably just try.
>
> ->I think it would be nice if such a feature, if ever implemented,
> should preferably also be an option. Just ask driver if it can do this,
> and if not, fallback to single buffering as it is now. (Depends on
> graphicsRAM available, and engine capabilities for virtual height)
>
> Rudolf.
>
>
>
|

|