On 2011-06-09 at 04:30:08 [+0200], Rene Gollent <anevilyak@xxxxxxxxx> wrote: > On Wed, Jun 8, 2011 at 10:24 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > A BMessenger based solution would actually work with two changes: > > * The BMessenger would already need to be initialized in > > GraphicalUserInterface::Init() right after creating the window. > > * BMessenger::LockTarget[WithTimeout]() need to be fixed to recheck > > whether the right target was locked. > > Presumably that would be a matter of storing the looper's thread ID at > messenger creation time and verifying that they still match at point > of lock request? BMessenger already stores the port ID, which uniquely identifies the looper. It's just a matter of verifying that the locked looper's port ID matches. CU, Ingo