[Openmcl-devel] openmcl 1.0 vs. GUI

[Takehiko Abe]

David Steuber wrote:

> [...] The only difficulty I have 
> that really annoys me (and I have no clue as to what a fix would be) is 
> if something in the main thread (where the GUI must reside) signals an 
> error to send me to the debugger.  SLDB will come up and then never go 
> away.

I have a similar problem with CarbonEvent in MCL. I was wondering
how OpenMCL handles it -- non-local exit from an event callback.

> So I've used ignore-errors as a bandaid in my callback function. 
> The condition is logged in the grand tradition of printf style 
> debugging and the code plows on in the face of adversity.

Another solution is to avoid CarbonEvents as much as possible
and do event dispatching by yourself (like MCL does).