how about using mayapy? then you have full access to python to do whatever you want. write it out to file, pickle it, get ridiculous and use sockets, generally do whatever.
just a side thought, i started using nuke's python, and it really made me appreciate how strong the foundation of maya's python implementation is. the details were wanting, but i really took the strengths of mayapy for granted. Nuke 5.0 had nothing like that, and nuke 5.1 has only a partial solution. -chad On Sep 5, 2008, at 12:49 PM, John Creson wrote: > > how about writing the stdout to a file and reading that? > > mayabatch -log "C:\temp\mayaOut.txt" -prompt > > On Fri, Sep 5, 2008 at 1:40 PM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: >> >> I'm making a call to mayaBatch to query out some scene information >> without having to actually GUI-open the scene. I make the call using >> os.system as was wondering if there was an easy way to store the >> stdout in a variable. >> >> So the mayaBatch call is using -prompt and then -command to query the >> info from the given scene file. >> >> I've seen some various methods on the web that apparently allow you >> to >> capture the output like subprocess and popen. My problem with these >> is >> that the apparently stored information in my variable output isn't >> readable. >> >> As I'm writing this I just thought of the possibility of using the >> "command" to just store the info I need in a maya variable or >> optionVar or something. I might try this though I don't know if the >> variable will be accessible from the batch. >> >> Anyways, if anyone has any advice in this matter please let me know. >> The need is to get some render information from a scene without >> having >> to open it and make it accessible to my script running in maya. >> >> Thanks >> -Riddle >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ Yours, Maya-Python Club Team. -~----------~----~----~----~------~----~------~--~---
