[Fluxus] every-frame & frame hooks

[Scott]

On Tue, Apr 14, 2009 at 10:03 AM, Scott <alcoholiday at gmail.com> wrote:

> Yep!
> Look for spawn-task in the e-mail archive.
> But basically -
>
> > (spawn-task foo 'bar)
> > (spawn-task (lambda () (draw-cube)) 'cube)
> > (ls-tasks)
> task: bar #<procedure:foo>
> task: cube #<procedure>
> > (rm-task 'bar)
>
> These "tasks" (they are currently just thunks... but I may get around to
> adding continuation support), will catch errors and keep TRYING to run until
> they are rm'd (they can rm themselves, which can be useful). Oh - and there
> are 'timed tasks' for doing things in the future... check out tasks.ss for
> deets.
>
>
> On Tue, Apr 14, 2009 at 8:59 AM, nik gaffney <nik at fo.am> wrote:
>
>> hi all,.
>>
>> i remember some relatively recent discussion about either including (or
>> avoiding) frame hooks or timer functions as an alternate way of running
>> a handler for multiple functions from every-frame,
>>
>> was this resolved either way? is there currently a standard way to run
>> multiple functions each frame, or at a regular interval?
>>
>> nik
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20090414/f06677ca/attachment-0001.html>