Aha, exactly as you say,
geo_hash[DD::Image::Group_Points].append(
input(1)->GeoOp::hash(DD::Image::Group_Points));
..was what I was looking for - thanks!
On 27/10/11 03:07, Jonathan Egstad wrote:
> I think the Op::append() handles this automatically, but for geometry hash
> specifics:
>
> Include the input(x)->hash() into the appropriate geometry hash. For example
> if it's a GeoOp that distorts geometry based on an input Iop then the Iop's
> hash would be included in the Group_Points hash (if only the point positions
> are affected.)
>
> If the inputs are GeoOps then you should append all the hashes from the input
> GeoOp into your own (loop through the hash list appending each
> input(x)->GeoOp::hash(n) to your geo_hash[n].)
>
> -jonathan
>
> On Oct 26, 2011, at 3:02 AM, Ben Dickson wrote:
>
>> Another easily caching related question:
>>
>> If I have a GeoOp'ish node with more inputs, how do I get the node to
>> respect hash changes on the secondary inputs?
>> --
>> ben dickson
>> 2D TD | [email protected]
>> rising sun pictures | www.rsp.com.au
>> _______________________________________________
>> Nuke-dev mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>
> _______________________________________________
> Nuke-dev mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
--
ben dickson
2D TD | [email protected]
rising sun pictures | www.rsp.com.au
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
