Ouch!
It seems that I MUST declare the property as dynamic but I MUST NOT implement
it because the superclass does it for me.
This is of course very crafty but very different of how I used dynamic
properties up to now, so it took me some time to wrap my head around it...
On 07.09.2011, at 09:27, Sebastian Mecklenburg wrote:
> Hello,
>
> Im getting started with custom patch programming and I'm writing a simple
> sine LFO for a start. However, it always outputs zero.
> I set the execution mode to kQCPlugInExecutionModeProcessor and the time mode
> to kQCPlugInTimeModeTimeBase;
> Then I created a dynamic output value parameter where I return the value
> computed in execute: t atTime: withArguments:
>
> Debugging shows that execute is called repeatedly and that the value is
> computed correctly but the value in never requested from the next patch. When
> I hook up the built in LFO it works fine.
>
> so, in the header I have
>
> #include "Oscillator.h"
> @interface OSCPluginPlugIn : QCPlugIn {
> double myComputedValue;
> }
> @property (assign) double outputValue;
> @end
>
> and the implementation basically is
>
> @implementation OSCPluginPlugIn
> @dynamic outputValue;
> - (double)outputValue {
> //this is never called
> return myComputedValue;
> }
> - (BOOL)execute:(id <QCPlugInContext>)context atTime:(NSTimeInterval)time
> withArguments:(NSDictionary *)arguments {
> myComputedValue = sin(time);
> return YES;
> }
> @end
>
> This all looks pretty straightforward to me. What am I doing wrong?
>
> Thanks and regards,
> Sebastian Mecklenburg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
