[interfacekit] Re: :) Again - BBitmap/BWindow
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Fri, 25 Jul 2003 18:21:45 +0200 CEST
On Fri, 25 Jul 2003 10:49:17 +0300 "Adi Oanca" <adioanca@xxxxxxxxxxxxx>
wrote:
> > > Couldn't this approach be used for windows as well?
> > > Not that I would say do it now :)
> >
> > I guess it could. But since the communication traffic for windows
> > should be much higher, we would probably lose performance.
>
> Mmm... haven't thought about that! I don't think the performance
> hit
> would be noticeable. That is because it's only the window that has
> the focus
> who gets the most messages, the others... merely get pulse
> messages(if they
> do)!
If you move a window, the windows below need to update themselves as
quickly as possible. Especially in such cases the visual feedback may
suffer, if multiplexing is done.
I totally agree that most windows do close to nothing almost all the
time, but it's also on hot spots, when they must behave properly.
> I also think that in this case we should monitor traffic, and where
> it
> gets higher, we should let one thread per window; but also have a
> restriction of... 5(?) BWindows per thread!(In other words: A dynamic
> port
> [re]allocation schema). I don't know, we should make a test!
I'm a bit sceptical about being closefisted regarding window resources.
I completely see the need for being economical with bitmaps, since the
bitmap itself can be a cheap resource (only a bit of memory for small
bitmaps), but a window is relatively dear on application side, anyway.
CU, Ingo
- References:
- [interfacekit] Re: :) Again - BBitmap/BWindow
- From: Adi Oanca
Other related posts:
- » [interfacekit] Re: :) Again - BBitmap/BWindow
- » [interfacekit] Re: :) Again - BBitmap/BWindow
- [interfacekit] Re: :) Again - BBitmap/BWindow
- From: Adi Oanca