Hi all,

I would be very interested if there is anyway to manage this localising in
background.
I've also tested to use the threading method and found the same
problem/cause as Frank.


Justin


2013/12/13 Howard Jones <mrhowardjo...@yahoo.com>

> Thanks for testing. That would have stumped me.
>
> I contacted support.
>
> Howard
>
> On 12 Dec 2013, at 23:48, Frank Rueter <fr...@beingfrank.info> wrote:
>
> I remember now:
> I tried this a while ago myself and failed because doLocalise() is a
> wrapper function using nuke.localiseFiles which seems to be compiled.
> Since nuke.localiseFiles takes care of the progress bar (presumably
> juggling it's own threads) it's not just a matter of using
>
> thread = threading.Thread(target=doLocalise, args=(True,))
>
> thread.start()
>
> or
>
> thread = threading.Thread(target=nuke.localiseFiles, args=(readKnobList,))
>
> thread.start()
>
>
> Both the above do the job, but you won't get the progress bar and the main
> thread is still blocked.
>
> There might be a way but I don't know how, other than basically writing
> the localisation logic yourself.
> So best to push that feature request to make nuke.localiseFiles
> thread-able.
>
>
> Cheers,
> frank
>
>
>
> On 13/12/13 12:15, Frank Rueter wrote:
>
> Yes, you should be able to. I have a quick peek...
>
> On 13/12/13 11:29, Howard Jones wrote:
>
> Ok done. Out of interest can this be run in a separate thread? My python
> brain hasn't got round threading, but i can run doLocalise(0) so could I
> thread it instead?
>
> Howard
>
> On 12 Dec 2013, at 22:02, Frank Rueter 
> <fr...@beingfrank.info><fr...@beingfrank.info>wrote:
>
> I have asked for this in the pas as well, so please bug support to up the
> priority ;)
>
>
> On 11/12/13 05:23, Howard Jones wrote:
> Hi
> Is it possible to run localise from a shell or in the background?
> H
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
>
_______________________________________________
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

Reply via email to