[interfacekit] Re: deadlock with BApplication/BWindow

On 2005-03-14 at 00:59:06 [+0100], Axel Dörfler wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > done. Putting the window_quit_loop() code into a loop, as in you
> > proposal,
> > would at least make sure that there won't be any windows anymore that
> > have
> > been created from the app thread or any window thread. So this is
> > probably a
> > good idea.
> 
> What about an additional flag that avoids creating windows?

Good in theory, but probably of little help in practice. We don't use 
Exceptions, so the BWindow constructor can't report errors back. Run() 
could, but who ever checks its return value? On the other hand, it could as 
well just destroy the window before even starting the looper thread.

CU, Ingo

Other related posts: