[mcclim-devel] event handling outside the top-level loop
Hi *, I'm playing around with an mandelbrot explorer with an simple clim interface. This means the application spends a lot of time in an local loop[0]. During this time the interface is "dead" as no events are handled. So I would like to trigger the event handling from time to time in my own code -- is there an easy way to do so? cheers sascha [0] actually an recursion with the algorithm I'm using -- Sascha Wilde Real programmers don't want "what you see is what you get", they want "you asked for it, you got it". They want editors that are terse, powerful, cryptic, and unforgiving. In a word, Teco.
On Mon, Mar 9, 2009 at 6:42 AM, Sascha Wilde <wilde@sha-bang.de> wrote:
I'm playing around with an mandelbrot explorer with an simple clim interface. This means the application spends a lot of time in an local loop[0]. During this time the interface is "dead" as no events are handled. So I would like to trigger the event handling from time to time in my own code -- is there an easy way to do so?
You can manually poll the event queue and dispatch any events that are present. This might look something like this*: (let ((queue (frame-event-queue frame))) (loop for event = (event-queue-read-no-hang queue) while event do (handle-event (event-sheet event) event))) This is not exactly equivalent to a CLIM app idle at its top level (notably, you're outside of the command loop, so interactor panes won't work at all), but should suffice for getting working repaint events, gadget callbacks, scroll bars, etc. *Disclaimer: I haven't tried this code.
participants (2)
-
Andy Hefner -
Sascha Wilde