Hi.

I think I stumbled on to a very odd bug with the Lighting patch while debugging 
something with a custom QC plugin.

For example. Make a new QC plugin. In the header add

@property (assign) NSString* inputPath;


In the implementation add the necessary
@dynamic inputPath;

make sure it is a Consumer ( kQCPlugInExecutionModeConsumer) and its time base 
is kQCPlugInTimeModeTimeBase so it triggers rendering/execution every frame.

and then in execute, add

    if([self didValueForInputKeyChange:@"inputPath"])
        NSLog(@"inputPath Changed");

Now, save, build/run/copy and then make a new composition - dont open the 
viewer yet. Add a lighting patch. Add our new patch inside the lighting patch 
and put something/anything in the textfield. Before you open the viewer, make 
sure you've simply enabled shadows.

Optionally Save the composition.

Now, start the viewer. Note that you did not see "inputPath Changed" printed. 
Stop the viewer. Disable shadows. Change the text field string. Now run the 
viewer, note you do see "inputPath Changed" printed.

You can also simply open the viewer when shadow is enabled (after opening it 
fresh, or starting/stopping the viewer) and continuously edit the string, and 
never see anything reported in the log (no change being reported). However, 
disabling shadows immediately makes your changes noticed. All the while the 
patch was indeed executing (add a log in the top of executeAtTime: to verify 
yourself)

Even more damning, you can disable shadows after having it off, see the changes 
being logged as you type, and then enable shadows, and see it ignore any 
changes you type. Its basically a live checkbox to ignore 
'didValueForInputKeyChange

Am I crazy? Is it late and ought I be asleep?

Thanks.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to