Can't speak for others, but here it was a feature asked by the artist. At the end of the day, they had to fill a log with all the shots / time worked during the day. Now all they have to do is to generate a log and edit the time if they think something calculated wrong.
All depends on what you do with the script. But certainly should be a script to spy on the artist On Thursday, September 22, 2011 8:22 AM, "Nathan Rusch" <nathan_ru...@hotmail.com> wrote: I’m going to suggest you reconsider, unless I’m completely misreading the intended purpose of this script. If any of your artists find out you’re doing something like this (even if you’re able to make it a reliable source of information, which I’m not sold on), they will likely resent and distrust you. If you suspect you’ve got artists who are legitimately slacking off on the job, just go talk to them. Plus, they could just write a simple loop to make it look like they’re working. -Nathan From: [1]Kasper Oerlemans Sent: Thursday, September 22, 2011 8:13 AM To: [2]Nuke Python discussion 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 <[3]mrhowardjo...@yahoo.com> 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 <[4]kasper.oerlem...@gmail.com> To: Nuke Python discussion <[5]nuke-python@support.thefoundry.co.uk> 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 <[6]jav...@gmail.com> 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 [7]Nuke-python@support.thefoundry.co.uk, [8]http://forums.thefoundry.co.uk/ [9]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nu ke-python _______________________________________________ Nuke-python mailing list [10]Nuke-python@support.thefoundry.co.uk, [11]http://forums.thefoundry.co.uk/ [12]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke -python _______________________________________________ Nuke-python mailing list [13]Nuke-python@support.thefoundry.co.uk, [14]http://forums.thefoundry.co.uk/ [15]http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/n uke-python ____________________________________________________________ _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-pyt hon _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python References 1. mailto:kasper.oerlem...@gmail.com 2. mailto:nuke-python@support.thefoundry.co.uk 3. mailto:mrhowardjo...@yahoo.com 4. mailto:kasper.oerlem...@gmail.com 5. mailto:nuke-python@support.thefoundry.co.uk 6. mailto:jav...@gmail.com 7. mailto:Nuke-python@support.thefoundry.co.uk 8. http://forums.thefoundry.co.uk/ 9. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 10. mailto:Nuke-python@support.thefoundry.co.uk 11. http://forums.thefoundry.co.uk/ 12. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python 13. mailto:Nuke-python@support.thefoundry.co.uk 14. http://forums.thefoundry.co.uk/ 15. http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- Hugo Léveillé TD Compositing, Vision Globale hu...@fastmail.net
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
