I'm not sure if it's still the case, but one version used to pipe the
function call through mel, something like this (only a lot more OOP and with
better error handling etc...):
callbackData = None
def _doRunCallback():
global callbackData
someFunc, args, kwargs = callbackData
Has anyone tried using undoInfo -openChunk and undoInfo -closeChunk to
work around this?
On Fri, Feb 5, 2010 at 4:44 AM, Ofer Koren kor...@gmail.com wrote:
I'm not sure if it's still the case, but one version used to pipe the
function call through mel, something like this (only a lot more OOP
Hi,
I'd like to use the addAttributeChangedCallback function of the
MNodeMessage class, to be able to monitor all attribute changes in the
scene.
I'm having problems with the Pyhon API syntax of this class, does any of
you have a simple example that displays the correct syntax?
Any help is
Unless I'm missing something about your question, you can just copy-
paste them from my wiki link above. The full source is right on that
page. And if you're using Wing Pro, then yes, you can use that code
per the wiki to have Wing talk to Maya.
On Feb 4, 10:54 pm, Subbu.Add subbu@gmail.com
I mean 0.7.8, we have teams still on 8.5. Guess I could try to enforce
a SP1 upgrade, and go w/ 0.9.
Maybe I'll try Paul's suggestion, just for kicks. See if it works.
-jason
On Feb 4, 10:42 pm, Chad Dombrova chad...@gmail.com wrote:
do you mean 0.7 or 0.9? because 0.7 is really old. on our
Manual Method 4: sitecustomize
...
4. save this file as sitecustomize.py somewhere in your system python
path.
Only the default maya install locations, (*) paths, seem to inject
pymel path early enough, so you might as well use Method 3: pymel.pth.
(*)C:\Program Files\Autodesk\Maya2008\bin
I've been doing this for sometime with great success. We currently
insert pymel (from a network location) to the front of the path with
sitecustomize. What is in your sitecustomize.py file? and are you sure
that it is being executed?
I have a print at the top of mine which you should see in the
Ian,
Tried to reply earlier, but don't know if it went through. Google
groups delays the post sometimes.
My sitecustomize.py is just like the instructions:
import sys
sys.path.insert(0,'Y:/Tools/SOEmayaTools/python/pymel-1.0.0rc1')
It is only being executed in these default maya install paths:
Looks like what is inside your sitecustomize.py file is correct
(assuming the paths etc are all spelled correctly) which means that
the sitecustomize.py file is likely not in your PYTHONPATH by the time
maya starts. The folder containing sitecustomize must be in the
PYTHONPATH when the python
OK, that's what I suspected.
Just wanted to make sure there wasn't some easier way.
I think I'm going w/ Maya.env hack as the path needs to change per
version of Maya. I cannot have 1 path designated for the entire
machine.
Appreciate your responses,
-jason
On Feb 5, 4:46 pm, Ian Jones
Thanks Mr. Eric.
Now Am able to send text as command to Maya.
So that from wing, with string assignment to txt variable,
now it is possible to create sphere in Maya from wing.
txt = 'sphere()' # in def send_to_maya(language)
since 'getWingText()' is not working due to wingapi module is
Dear Mr.Eric,
I have got the module wingapi in the below path,
C:\Program Files\Wing IDE 3.2\bin
But still it is not getting imported.
Which is the right place for modules in wing to get imported?
By getting the content from wingapi, executed in wing.
Even same problem with:
import edit.editor
12 matches
Mail list logo
