Even better when you consider that the artist can have 5 openned nuke and that if they don't use one particular session for hours, this session will be considered idle
On Thursday, September 22, 2011 5:35 PM, "Kasper Oerlemans" <[email protected]> wrote: I'm going to be the evil overmaster and my artist are going to be my little slaves!!!!! Whaaaahhhhaaaaa (evil laughter)!! No seriously, it's exactly what Hugo says. It's meant to make life easier for the artist so they don't have to fill in some long list at the end of the day and we don't forget about some shots etc. Great idea Hugo to just monitor the autosave!! Greetings! Kasper On Thu, Sep 22, 2011 at 5:29 PM, Howard Jones <[1][email protected]> wrote: Try more like an hour for anything complex Howard ____________________________________________________________ From: Kasper Oerlemans <[2][email protected]> To: Nuke Python discussion <[3][email protected]> Sent: Thursday, 22 September 2011, 16:13 Subject: Re: [Nuke-python] detect idle time I think I will start the counter after 10 minutes of idle time, that should be enough to all those things you mention ;-) Groetjes! Kasper On Thu, Sep 22, 2011 at 3:31 PM, Howard Jones <[4][email protected]> wrote: Dont know but I'd be interested to know how you will be able to log little things like creative thought, problem discussions and overall shot reflection time, which in my experience go a bit towards the actual result ;) Howard ____________________________________________________________ From: Kasper Oerlemans <[5][email protected]> To: Nuke Python discussion <[6][email protected]> Sent: Thursday, 22 September 2011, 14:02 Subject: [Nuke-python] detect idle time Hi everyone, Got a question, I'm thinking about making a script that logs the amount of time my artist are really working in a specific comp. So I need a way to detect if they are doing anything in the comp like changing parameters, moving nodes, moving vertices of roto etc. I've found that I can log some of these things by adding a function to updateUI but this one isn't triggered when you move to a new frame or move a node around. Does anyone have an idea how to pull this off? Or if there are any other functions that can be useful? Thanks! Greetings! Kasper On Wed, Sep 14, 2011 at 11:34 PM, Javier Garcia <[7][email protected]> wrote: Hi, I need to trigger the autolabel callback from other callback, for example: def onInputChangeCallback(): nuke.frame( nuke.frame() + 1 ) # this line will trigger the autolabel callback but also will change the current frame, nuke.frame( nuke.frame() ) doesn´t work. def autolabelCallback(): if node_input == XX: return 'XXXX' else: return 'YYYY' thanks. J _______________________________________________ Nuke-python mailing list [8][email protected], [9]http://forums.thefoundry.co.uk/ [10]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/n uke-python _______________________________________________ Nuke-python mailing list [11][email protected], [12]http://forums.thefoundry.co.uk/ [13]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke -python _______________________________________________ Nuke-python mailing list [14][email protected], [15]http://forums.thefoundry.co.uk/ [16]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/n uke-python _______________________________________________ Nuke-python mailing list [17][email protected], [18]http://forums.thefoundry.co.uk/ [19]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke -python _______________________________________________ Nuke-python mailing list [20][email protected], [21]http://forums.thefoundry.co.uk/ [22]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/n uke-python _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python References 1. mailto:[email protected] 2. mailto:[email protected] 3. mailto:[email protected] 4. mailto:[email protected] 5. mailto:[email protected] 6. mailto:[email protected] 7. mailto:[email protected] 8. mailto:[email protected] 9. http://forums.thefoundry.co.uk/ 10. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 11. mailto:[email protected] 12. http://forums.thefoundry.co.uk/ 13. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 14. mailto:[email protected] 15. http://forums.thefoundry.co.uk/ 16. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 17. mailto:[email protected] 18. http://forums.thefoundry.co.uk/ 19. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 20. mailto:[email protected] 21. http://forums.thefoundry.co.uk/ 22. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- Hugo Léveillé TD Compositing, Vision Globale [email protected]
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
