[interfacekit] Re: BLooper extensions

"Axel D=F6rfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
> 
> "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > For the future, when we have something like the now often 
> > > mentioned 
> > > wait=3D3D5Ffor=3D3D5Fmultiple=3D3D5Fobjects(), I would prefer something 
> > > like:
> > > BLooper::AddPort(port id);
> > Sounds good. Maybe can be even
> >   BLooper::AddPort(port id, float priority =3D3D 0.5)
> > if that can be supported.
> 
> That wouldn't really be necessary with wait=5Ffor=5Fmultiple=5Fobjects(), 
> right=3F

The priority wouldn't be of relevance for waiting for messages, but for 
fetching the messages from the port. I.e. if there are messages waiting 
at two ports, the port with the higher priority would be served first. 
If I understood it correctly, the messages arriving at a BWindow's app 
server port should have priority over the looper messages.

> > > along with an extended form of BLooper::GetMessageFromPort() 
> > > which 
> > > specifies the port number or something like this.
> > Why would that be needed=3D3F Or do you intend it to be BLooper 
> > private
> > =3D3F
> 
> As you obviously already realized, it could convert the incoming 
> messages to real BMessages.

Yep, that was clear, but not that the method would be virtual and could 
be overridden by derived classes, if a special handling was required. :
-)

CU, Ingo

Other related posts: