[interfacekit] Re: BLooper - PLEASE look at...

"Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> "Erik Jaesler" <erik@xxxxxxxxxxxxxx> wrote:
> > I'm going to weigh in with Axel and Ingo on this; sorry, Adi.  I 
> > had 
> > misgivings anyway, and Axel and Ingo have done a good job of 
> > articulating what I wasn't able to. I particularly like the idea of 
> > being able to simply add ports, although if I understand correctly, 
> > BWindow does some "special" processing on its messages from 
> > app=5Fserver; 
> > it might be nice to provide a way to accomplish that in the 
> > proposed 
> > API.
> Ah, right. Now I get, what Axel proposed the GetMessageFromPort() 
> for. 
> BWindow would override it and implement the `special' processing for 
> its port (otherwise letting the base class version do the job).

Exactly! :-)

> > When Adi and I were talking about this, I found myself wishing for 
> > wait=5Ffor=5Fmultiple=5Fobjects() -- I think that's the first time 
> > I've 
> > ever 
> > really wanted a Windows API available on BeOS. =3DP  Just out of 
> > curiousity, Axel, how much work do you think that will require in 
> > the 
> > kernel=3F
> That would be interesting. Though, it wouldn't harm, if we don't have 
> it for R1. We could do the polling thing for the time being and 
> replace 
> it as soon as the kernel provides the functionality.

I am not sure it would be good to have that BLooper functionality in R1 
- it would be nice if not needed that you could select a) the port it 
should poll on, and b) how long it should wait for an incoming message.
Both things would be crucial for a good performance, but would require 
additional API which had a very short life-span.

Adios...
   Axel.

Other related posts: