4 Feb
2013
4 Feb
'13
3:40 p.m.
On Feb 4, 2013, at 15:28, Jonathan Fischer Friberg odyssomay@gmail.com wrote:
Hi,
It seems that abcl is currently running on the awt thread. As when I get an error, it says something along the lines
"#<THREAD "AWT-EventQueue-0" {3C6B5}>"
This has some nasty side effects, namely:
- eval blocks the ui (until the eval has finished)
- On error, the version 1.1.0 locks down the ui completely. That is, the ui locks and doesn't come back.
So it would be nice if I could run abcl on it's own separate thread. Is such a thing possible?
I guess in worst case I'll have to start up a separate thread in the eval (that is, in common lisp), which I think would do what I want. I would prefer to have the whole of abcl in its' own thread though.
Naive question: how would this change influence GUI programming in ABCL? I assume (but could be wrong) that abcl might want to execute code on the awt thread in that case.
Rudi