>> delete the object from the canvas.  It looks like I have to schedule a 
>> removal, which communicates to the engine and then waits for a callback 
>> that finally removes it.  Something is being missed though, because it 
>> doesn't always remove.  Maybe if you take a look Tim you will know what 
>> I missed.  Otherwise I'll track it down.
> 
> i will have a look at it as soon, as i can clone your git repository :)

Sorry about that. I think this should work:

http://git.lifeisagraph.net/nova.git/

> i already tried to split up the engine communication from the drawing
> part ..
> 
> the engine-part of gobj classes is PatcherGobj, which is derived from he
> base class, that is exposed from the py_nova module. the drawing part
> for ordinary objects is the GObjBox class ...

Yeah, I saw a bit of this.  I need to figure out how communication and 
dispatching is working a bit better before I can contribute anything 
useful to the discussion.  How about creating a place on the wiki where 
we can take notes about these things as time goes on?  Sort of a working 
architecture page.

> hm ... there is an sfread~ object, playing sound files from the
> filesystem, but no sfwrite~ object for recording sound files ...

Cool.  I'll start with sfwrite~.

> or maybe you want to port fiddle~? :)

I think that might be a bit much for starting off.  Fiddle uses an fft 
though, so maybe I'll look into doing ffts next...

-Jeff
_______________________________________________
nova-dev mailing list
[email protected]
http://klingt.org/cgi-bin/mailman/listinfo/nova-dev
http://tim.klingt.org/nova

Reply via email to