15 Jun
2007
15 Jun
'07
8:52 p.m.
On Fri, 2007-06-15 at 15:16 +0200, Fons Adriaensen wrote:
On Fri, Jun 15, 2007 at 03:05:54PM +0200, Fons
Adriaensen wrote:
I tend to agree with Fons on this one but I just want to thank Tim
for finding the problem. I kept running into that one a week or so ago
and I thought I was losing my mind. It kept moving on me. No wonder
since it was using random stuff in memory.
Jan
--
Jan 'Evil Twin' Depner
http://www.thecfband.com
"Life should NOT be a journey to the grave with the intention of
arriving safely in an attractive and well preserved body, but rather to
skid in sideways, chardonnay in one hand, chocolate in the other, body
thoroughly used up, totally worn out, and screaming 'WOO HOO, what a ride'"
On Fri, Jun 15, 2007 at 02:08:17PM +0200, Tim
Goetze wrote:
Also consider that activate() and run() are normally called from
different threads and contexts, again complicating any coordination
between the two.
Let's assume the host provides the values
that are going to be used at
run() right when activate() is called.
They may not be available. Or they could change in between the
activate() and the first run(). In the latter case nothing is
solved, your first run() will interpolate again. To avoid that,
the host would have to delay any parameter updates until after
the first run(), and that is considerably more complicated than
a simple flag in the plugin. It would force the host to keep
two paramters sets to start with.