[interfacekit] BLooper extensions
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: "OpenBeOS Interface Kit" <interfacekit@xxxxxxxxxxxxx>
- Date: Fri, 23 May 2003 20:00:49 +0200 CEST
I am not too fond towards that extension to BLooper. It's only very
rarely needed to do something like this in real life, so it's not
urgently needed right now. We own BLooper and BWindow, so we can just
implement task=5Flooper() two times, I wouldn't have any problems with
that.
For the future, when we have something like the now often mentioned
wait=5Ffor=5Fmultiple=5Fobjects(), I would prefer something like:
BLooper::AddPort(port id);
along with an extended form of BLooper::GetMessageFromPort() which
specifies the port number or something like this.
BTW the original BWindow *does* overload BLooper::task=5Flooper() so I
think binary compatibility might require us to do that, too (windows
that inherit from BWindow rely on it).
Adios...
Axel.
- Follow-Ups:
- [interfacekit] Re: BLooper extensions
- From: Ingo Weinhold
Other related posts:
- » [interfacekit] BLooper extensions
- » [interfacekit] Re: BLooper extensions
- » [interfacekit] Re: BLooper extensions
- » [interfacekit] Re: BLooper extensions
- [interfacekit] Re: BLooper extensions
- From: Ingo Weinhold