Hmm. 1st I've heard of daemonic. I'll give it a go tomorrow.
Cheers
-Dave
On Wed, Sep 16, 2009 at 2:52 PM, Chris G wrote:
>
> Have you tried setting Thread.deamon / Thread.setDaemon() ?
> If the thread is not daemonic, it may block python finalization.
>
> -Chris
>
> On Wed, Sep 16, 2009 at
Hey drake -
First of all, for commands from plugins, BOTH a python command and a
mel command should be made. So, both of these should be valid:
// From mel:
mtor(...)
# From python:
import maya.cmds
maya.cmds.mtor(...)
Also, if you encounter problems with pymel.mel's wrapping, you can
always f
Have you tried setting Thread.deamon / Thread.setDaemon() ?
If the thread is not daemonic, it may block python finalization.
-Chris
On Wed, Sep 16, 2009 at 6:25 AM, thirstydevil wrote:
>
> I've noticed a few issues using PyQt and pumpThread. It seems that
> randomly when users closes Maya it w
I guess it is because mel command is not thread safe while python
makes use lots of threading stuff. Therefore, you can try to use of
maya.utils or the corresponds in pymel.
-- Drake
On Sep 4, 9:58 pm, Gregg wrote:
> Hello everyone.
>
> I try to render a scene using python render command with M
It's a lovely design to use 'mel.ooxx(...)' to invoke mel function as
'ooxx ...' but we encountered one special case as Pixar's mtor
function. In mel, mtor's function works like these:
mtor control getvalue -sync;
mtor control getvalue -rg dspyName;
mtor control setvalue -rg "dspyQuantizeOne" -va
I've noticed a few issues using PyQt and pumpThread. It seems that
randomly when users closes Maya it will do 1 of these:
1) Close successfully.
2) Not closes. Instead require 2 close requests by the user.
3) Closes but leaves 1 Maya thread running ( the pumpThread ) and
still consuming Maya's m
