Delayed evaluation of certain python commands & script editor feedback with 2011?

Delayed evaluation of certain python commands & script editor feedback with 2011?

sebastienpaviot
Participant Participant
390 Views
1 Reply
Message 1 of 2

Delayed evaluation of certain python commands & script editor feedback with 2011?

sebastienpaviot
Participant
Participant
Hi,
I am trying to debug a script of mine and understand why it crashes maya 2011 while it was working fine since 2008.

the script is still crashing a Maya 2011 trial (32bit under xp64) I have running on a PC without any real clear reason why. From the output of debug data into a file I managed to get, the reason for the script to totally crash Maya are still unclear.

Furthermore, the exact same code is working with a Maya 2011 (64bit under win7 64b) on another PC, but with some weird behavior. Since Maya was not crashing anymore, I scattered my script with outputs of debug info to the script editor with variables and state throughout my code.
I was able to identify a point in the code where things aren't being updated as they should, but again without any clear reason as to why this was happening.
From the output I get in the script editor, my prints aren't logged in the script editor in the order they *should*.
To compare, I ran the exact same code with Maya 2009 (which I developed the script with). The script is behaving as it should, and the prints are logged in the right order in the script editor.

I am using a complex draggerContext for this script, and I would be interested to know how the UI changes from 2011 were implemented back into the draggerContext. And could it be possible the various events for this context aren't running in the same way they were previously to Qt?
Also, is the script editor not synced up with what's going on in Maya internally so there could be a discrepancies between what's been run and what's being echoed into the logs?
0 Likes
391 Views
1 Reply
Reply (1)
Message 2 of 2

sebastienpaviot
Participant
Participant
opened a thread about this on the subscription forums as it seems something fishy indeed is happening with re-entrance of event commands while previous operations aren't finished.
0 Likes