4 Feb
2003
4 Feb
'03
9:16 p.m.
Add a flag
that says they are a wrapper, and a flag on the control
that changes the universe? What if it is multiple controls?
*Now* I actually get what you're talking about. ;-)
Audiality running as a XAP plugin would be a typical example, as it
Anyway, it's even more hairy than it may look at first. Not only does
the plugin change appearance when you fiddle with certain controls;
that may also result in *connected* controls disappearin in thin air! The host
still
only calls run(), but if you provide those, it can use you without
a send-return loop. Is that good enough?
Sounds ok to me, although it doesn't allow for much flexibility for
plugins that want to make use of this. For example, you can't have a
hardcoded replacing version unless you also have the full "scale both
old and output" version.
Why? Because you need to support the MIX_DRY control to be able to
tell when the host wants you to do pure replace processing. I'm thinking about "CAN_<feature>"
style hints, some enum control and
stuff, but no good ideas so far...
All these 'flags' may be better off as
descriptor->meta_flag(XAP_CAN_INPLACE) style stuff, rather than bitmasks.
But simpler is better. Simpler is better.
My new mantra
Simpler is better