[fluxus] interactivity issues

[nik gaffney]

>> the example script works the other way round, checks if the mouse is over
>> an object and only does something if it is. 
> 
> Mmm, but this only works for trivial "somethings to do" - it's hard to
> do anything complex if you can't find (by comparison operations) which
> 'concept' in the scheme world the object you clicked on corresponds to.

hmmm.. how about if the trivial something was to check an id (stored as a number
in an alist, when the 'actor' is created for example) which if sucessful, calls
a single function, using the id. to avoid further complexity related to events,
perhaps store any state in whatever data strucutre you are using for each
instance of the actors.
 
nzk