[haiku-appserver] Re: DisableUpdates() / EnableUpdates()

  • From: "DarkWyrm" <darkwyrm@xxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Sat, 29 Oct 2005 08:23:23 -0400 EDT

> Hi,
>       I have a problem with these methods:
> DisableUpdates() , EnableUpdates()
>       These functions disable automatic updating within the window, and 
> re-enable it again. Any drawing that's done while updates are 
> disabled 
> is suppressed until updates are re-enabled. If you're doing a lot of 
> drawing within the window, and you want the results of the drawing to 
> appear all at once, you should disable updates, draw, and then re-
> enable 
> updates.
>       How do you think we should implement this? Do you how this is 
> implemented in R5? Any other information related to these 2 methods?
>       I think that to do what the BeBook says ("the drawing to appear all 
> at 
> once") we should draw in a bitmap and when EnableUpdates() is called, 
> copy/blit that bitmap in window's visible area.
>       Thoughts? Opinions?
Not that my opinion counts much anymore on the server (I'm *so* out of 
the loop) I'm more inclined to think that it might be better to queue 
the messages somehow. When working with a bitmap, we lose all benefits 
of HW acceleration.


Other related posts: