Heh, that's good to know. On Fri, Aug 17, 2012 at 4:00 AM, Peter Crossley <[email protected]>wrote:
> Hi Hugo, > > The caching functionality is built on top of the standard file knob, but > doesn't reimplement value() or evaluate(), so when you call these functions > directly on the knob you're calling through to the (uncached) file knob's > versions. > > Calling print nuke.selectedNode() is taking a different route through the > code which solves the local cache path, which is why you're seeing that > version of the path there. > > However this functionality isn't directly exposed through Python at the > moment. It should be possible to add, so if you'd like to see it please log > a feature request with support. > > Regards, > > Peter. > > > On 16/08/2012 16:08, Hugo Léveillé wrote: > >> I just noticed something strange this morning while trying to extract >> the path of the cache of a selected read. If you type: >> >> print nuke.selectedNode()['file'].**value() : you get the network path as >> expected >> >> print nuke.selectedNode()['file'].**evaluate() : same thing but with >> solved expressions >> >> But if you do print nuke.selectedNode() and look at the output, you get >> the path of the local cache. I know I can easily reconstruct the path of >> where the cache is, but was wondering, since I see that the path is >> already solved in the print statement, if there was a function to get >> that path directly. >> >> >> > ______________________________**_________________ > Nuke-python mailing list > Nuke-python@support.**thefoundry.co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-python<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
