Hi,<div><br></div><div>Lispbuilder has some known problems running on CCL OS X. Recently a user pointed out that the failures seen in CCL can be duplicated in SBCL by starting lispbuilder in a new thread. Our guess is that cocoa doesn't like being called from any thread other than the initial thread. (Lispbuilder uses a portable wrapper around cocoa.) I'm wondering if there is any way to arrange to have our cocoa code run in the initial thread (preferably without having to rewrite the existing wrapper)?<br clear="all">
<br></div><div>Thanks.</div><div><br>-- <br>Elliott Slaughter<br><br>"Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay<br>
</div>