Re: [scripting] Where an operator reads.

Date : Thu, 19 Jan 2006 18:47:10 -0500
To : <XSI(at)Softimage.COM>
From : <francois.painchaud(at)sympatico.ca>
Subject : Re: [scripting] Where an operator reads.
Salut,

Have you considered using the ConstructionHistory object:

"This object represents the operator stack for a Primitive object. It allows you to browse through the stack one operator at a time by enumerating the ConstructionHistory object, which you can get with the ConstructionHistory (Primitive) property."

François

> De: Francois Lord <francoislord(at)gmail.com>
> Date: 2006/01/19 jeu. PM 06:12:37 GMT-05:00
> À: XSI(at)Softimage.COM
> Objet: [scripting] Where an operator reads.
> 
> Does anyone know how to figure where an operator is reading in the stack 
> (like the tooltip for TextureOps) in scripting?
> I need to know that for any kind of operator that can be applied on 
> ClusterProperties (TextureOp, Weight Map Generator, Weight painter, 
> Automatic Envelope Assignment, etc.).
> 
> I'm writing a SceneCleaner plugin, and I want to freeze some operators 
> automatically. For example, an Automatic Envelope Assignment operator 
> should always be frozen if there are no other operators under it (unless 
> you're working with a very whacked-up rig). I just can't figure if there 
> are operators under it.
> 
> Any Idea?


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.