composite and smooth moving (double buffering?)

[Anders Storsveen]

Michel Dänzer wrote:

>On Wed, 2005-10-05 at 20:45 +0200, Anders Storsveen wrote:
>  
>
>>Michel Dänzer wrote:
>>
>>    
>>
>>>On Wed, 2005-10-05 at 08:48 +0200, Anders Storsveen wrote:
>>> 
>>>      
>>>
>>>>Another observation here is, what I mean by smooth, but slow is that. If
>>>>I move a window that I feel is smooth around, like konq or kcontrol, it
>>>>moves with a kind of lag, like if I move my mouse from point a to point
>>>>b, when I'm finished moving the mouse, the window comes
>>>>"dragging"-after. Like if I use TIME to move the mouse, the window uses
>>>>TIME+(SMALLTIME) :) however xterm, and konq, and even konsole is instant.
>>>>        
>>>>
>>>In that case, the tearing is probably just not noticeable due to the
>>>slowness (which is probably due to the operation not being fully
>>>accelerated).
>>>
>>>      
>>>
>>My first thought was that it was slow, because it waited for all frames
>>to be rendered before sending it to the screen, [...]
>>    
>>
>
>There's no mechanism for that yet that I know of, and if there was, it
>would be really bad if it caused noticeable lag.
>
>
>  
>
I kinda of like it smooth, with the "hopes" of performance improving
with new drivers, or optimizations ;) weird that there's no mechanism
though. Are you sure it isn't just a bi-effect of using the compositer,
that it gets drawn error-free?