[interfacekit] Re: BApplication (or, OBAppplication)
- From: DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Fri, 26 Apr 2002 16:59:19 -0400
>Does anyone have any insight on how to hijack the BLooper's default port
>for message-receiving in the BApplication class?
Not hard. The port's name is AppLooperPort. All you have to do is call
set_port_owner on the port you intend to steal.
>Obviously, the virtual Run() function must be overloaded (because
>otherwise the BApplication will spawn another thread. Then we lose
>(unfortunately) the loop which shunts messages from the port on over to
>the BMessageQueue.
>
>Fortuitously, it seems that BApplication is a friend of BLooper, giving
>it access to some of the private parts, but there must be a more elegant
>way of doing this.
>
>Isaac
You may or may not even need to do this. If the subject is any indicator, I *
have* a skeleton OBApplication and last I knew, I think Erik was working on
it.
--DW
- Follow-Ups:
- [interfacekit] Re: BApplication (or, OBAppplication)
- From: Erik Jaesler
- [interfacekit] Re: BApplication (or, OBAppplication)
- From: Isaac Yonemoto
- References:
- [interfacekit] BApplication (or, OBAppplication)
- From: Isaac Yonemoto
Other related posts:
- » [interfacekit] BApplication (or, OBAppplication)
- » [interfacekit] Re: BApplication (or, OBAppplication)
- » [interfacekit] Re: BApplication (or, OBAppplication)
- » [interfacekit] Re: BApplication (or, OBAppplication)
- [interfacekit] Re: BApplication (or, OBAppplication)
- From: Erik Jaesler
- [interfacekit] Re: BApplication (or, OBAppplication)
- From: Isaac Yonemoto
- [interfacekit] BApplication (or, OBAppplication)
- From: Isaac Yonemoto