Like the Qt pumpthread you mean ? Will it be evaluated even when Maya is not idle (during a playback for instance) ?
The couple of successful input device I saw for Maya (like that old midi => blend shapes control plugin) I think were built that way. Shame jlcVcrDevice pluging example which is still in the docs seems to be gone from the directories (or I didn't see it). Have all these been deprecated ? MPxMidiInputDevice would sound logical, by the methods on it it look like it's been used to provide a driver for these spacemouse things. You say you need an external library for these MDevent types? Olivier Chris G wrote: > Why not just use a python thread? > > On Wed, Feb 25, 2009 at 10:39 AM, Seth Gibson <[email protected] > <mailto:[email protected]>> wrote: > > I was actually looking at clock server myself for this very reason > and noticed that it uses some pretty specific headers > )<maya/mocap.h>, ditto with the MPxMidiInputDevice example (needs > a midi lib for events from what i can see). Does anyone know of > any python modules that might provide that sort of functionality? > > > On Wed, Feb 25, 2009 at 3:45 AM, Olivier Renouard > <[email protected] > <mailto:[email protected]>> wrote: > > I'd rather take a look at the mocap / clock server example in > the devkit if you want something that acts as a data source. > > What you said works Judd and it's a great way to setup fake > dynamics bones / nodes that evaluate each frame but when > writing a joystick / midi / gamepad controler I think the > server things is what is advised usually. > > > Judd Simantov wrote: >> I'm not sure how smart it is to do this, cause it definitely >> goes against the way the DG works, but if you create an >> MPxLocator node you can access a plug in your draw call and >> get or set the data in there. Again, its probably not the >> most clean thing to do, but I have done this on occasion when >> necessary. >> >> On Tue, Feb 24, 2009 at 2:18 PM, hapgilmore >> <[email protected] <mailto:[email protected]>> wrote: >> >> >> I'm creating a node that queries a gamepad (XB360 >> controller) and sets >> attributes that mirror button states. >> Everything works except that the compute must be manually >> triggered >> (by editing a dummy attribute). >> >> Is there a nice way to force the compute? can you make >> an attribute >> "dirty" every screen draw, or put it on a timer? >> >> I've thought about making a callback that waits a preset >> amount, and >> then edits the attr, which re-triggers the callback, >> making an >> infinite loop of sorts. Is that kosher? >> >> >> >> >> > > > -- > Olivier Renouard > > > > > > > > > > > -- Olivier Renouard --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
