This is normal behavior, because there is no Qt event processing if
you load the file from within the eql.exe (for interactive development
you must use Slime).
So, in order to have a running Qt event loop, you need to fire up a
command shell (either cmd.exe or PowerShell), and pass the file as
argument to the eql.exe, e.g:
(please note the slash, so don't use backslashes)
eql.exe examples/1-hello-world
> typing (eql:qgui)
> also shows a frozen window.
same here; you need to do:
eql.exe -qgui
> I have the same problem in emacs
in your ".emacs" file, did you add the command line argument "-slime"?
(setq inferior-lisp-program "/path-to-eql/eql -slime")
Paul
...another option would be to call (eql:qexec) afterwards, optionally
passing a timeout (in milliseconds) after which event processing will
stop.
But in Windows there is a problem here: trying to interrupt (Ctrl+C)
and continue (:c) the event loop from the command shell will work only
a first time... (I don't know why: in both Linux and OSX this is no
problem).
Paul
Well, if somebody isn't happy with EQL:
There is CommonQt: according to its website, it has been tested with
Clozure CL on Windows.
Paul
thank you, you're right of course:
the "quick" part is much more important than most folks realize...
(BTW, the "eql-win32.zip" only exists because of an explicit request
from a fellow Russian user)
Paul