Is It Possible To Disable Scriptjob Verbosity?

[kloveridge]

I have a scriptJob that is running as an idle event. Everything is fine except if I turn on Echo All Commands. At which point, the scriptJob repeats its call over and over. Is there a way to disable a scriptJob from outputting its command?

[ewerybody]

maybe put commandEcho -state off; ... commandEcho -state on; around your scriptJob command.

but doing an idle-scriptjob is a nasty thing. Are you sure you need that?

edit: oops. Seems that doesn't work. ;]

[kloveridge]

What I am doing is a hack.

I have written a MFC gui that runs on top of Maya. Everything has been fine for the last few months. But one of the things this gui needs to do is display the Hypershade window and/or the attribute editor.

To make a long story short, I have a bug somewhere in my code. Because when I attempt to open these two maya windows from the API, it causes a crash or a incorrectly drawn ui. Because we are in a bit of a hurry, I resolved the problem by setting up a scriptJob that "listens" to a global variable. when that variable is set, it fires of a mel script that displays the hypershade and/or the attribute window. No side effects--except if the echo all commands is set.

Its a hack with a minor nuisance. I'll have to eventually solve the real problem. But this will get us through our deadline for now.

[kloveridge]

I changed from an idle callback to a selection change callback. Still a hack, but less obnoxious.

[joojaa]

well you really shouldn't use events in maya programming ideology. Idle being the stupidest possible event to use for anything.

But this all depends on what your mfc gui does.

Would be better if you modified the code to listen to a dummy nodes attribute instead then you wouldn't need to launch events in vain. Or thet your api/mel code would launch a mel condition (read docs on condition). or you created your won event type with MEvent