21:00:51jackdanielACTION looks suspiciously from hiding how the situation progresses
21:39:18slyrus1jackdaniels there's a circular dependency problem on your branch. compiling utils.lisp gives undefined variable: CLIM:+NOWHERE+, which is defined in design.lisp, which depends on utils.lisp.
21:45:24jackdanielis it a circular dependency (in contrast to forward reference)?
21:48:53jackdanielI will fix this forward reference of course, thanks for noticing that
22:04:11slyrus1good night! It's possible that it's just a font issue, but on this new box here when I click on an entry in the drawing-test test chooser, the entry "disappears". Not sure if that's a regression or not. (I doubt it, but I'll check).
22:06:27slyrus1But some code somewhere is probably missing some sort of warning about a font error.
4:09:33lokeWhat is the “correct” way to send asynchronous messages to a CLIM thread? (I.e. I have a UI that needs to be updated in real-time based on some external event in a different thread)
4:09:55lokeJust pushing an event to the event queue of the application in question?
7:25:44jackdanielloke: there is no correct way at the moment, both event-queue and stream access are prone to races and/or corruption. you must do it from the same thread as the event loop
7:26:19jackdanielstream in the application thread, event queue in the event loop thread **
7:26:26lokejackdaniel: Hmm, we have to introduce such a mechanism I guess.