starting an animation with the network

[forresto]

Re: #9 (bang!=>iip)

The clock animation now starts with the network, but I'm still not sure if this is the right way to do it. Kick's IN should be a bang, which shouldn't be settable in the ui. If it is settable in the ui, then we don't need Kick (just ban).

Do we need a different component that will just send one bang on network start? Pure Data calls this loadbang.

Re: meemoo/dataflow#62 (hiding inputs)

Now that inputs are hidden when connected you can stop the clock but can't start it again. (You can by changing the text in Kick IN, but that should be a bang.)

[bergie]

I'd handle this via meemoo/dataflow#78

[forresto]

That would be useful for more than just graph exports.

I'd vote for not hiding the inputs fields on connection (meemoo/dataflow#62), rather making another step (checkbox) to actually save an IIP. Then a checkbox on a bang port means loadbang.

[bergie]

Easy way for autostarting animations is to 'sidestep' the initial bang... you can modify the Clock graph for instance so that it is actually started by a core/Repeat node that receives a regular IIP (say, a string saying true, the contents of bangs don't matter) that then is sent to the in port of dom/RequestAnimationFrame, like so:

This has the effect of autostarting the animation.

[forresto]

So core/repeat can be used like Pure Data's loadbang.