That's OK now, I don't really know how...
I suppose this has bee solved using overriding the
void Iop::_request() method
On 04/17/2012 05:46 PM, Dorian Fevrier wrote:
Hi nuke community.
We are writting a .so plugin and have a strange behavior.
When we change a value in our plugin, it start to compute (this is
normal).
If we "do something" in the viewport (move, zoom, etc...), computation
stop and the image is shown unmodified (as if our node was disabled).
From this point, this is impossible to refresh and finish the
computation...
If I change a value and leave nuke do the computation, my image is as
expected. But if I get back to the old value (the one the computation
have not been finished), it doesn't compute!
It display the bad image, the one with no effect. I suppose all of
this is cache related.
But I've test with another plugin (not our) that have long computation
time: RSMB.
Even if I "do something" in the viewport (move, zoom, etc...), the
plugin still compute like if it was forcing nuke to "finish" computation.
I've read the classes documentation but did'nt find a way to force
nuke to "finish" node computation.
Any help is welcome.
Thanks in advance.
Regards,
Dorian
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
