Re: [LMMS-devel] unlinking automation objects

[Tobias D. <tob...@gm...>]

> It kind of works the way I expected in that when you
> unlink the objects, _object2 has a duplicate of
> _object1's pattern, and the two patterns can be
> independently edited.  However, once they are
> unlinked, automation doesn't work for _object2
> anymore.  What else needs to be done to get _object2
> to be automated?
I don't know, but may be you need to call syncAutomationPattern() for object2?

There's also a thing I noticed, that might need a fix (especially
@javier): in method "syncAutomationPattern()",
it->m_automation_pattern is assigned the value of
m_automation_pattern, but what if it->m_automation_pattern pointed to
a valid instance of an automation-pattern before? then you get
memory-leaks, i.e. one should delete it->m_automtion_pattern before
assigning a new value, or am I wrong? furthermore when passing
--with-ladspa to configure and having no ladspa-sdk installed,
configure just says that you should pass --with-ladspa to it instead
of giving the hint of the missing ladspa-sdk...

another bug in ladspa-effects: when removing a plugin while having it
controls-window open, the control-window remains and cannot be closed
anymore... you should check for an open control-window and close it in
effects-dtor :-)

I (hopefully) fixed the problems with generated files in CVS: I
removed all files that are generated and added Makefile.cvs so that
one only needs to run

make -f Makefile.cvs

and then configure and make should do well. Feedback is welcome ;-)

toby