- 1 Tool Pipeline
- 1.1 COM Interfaces
- 1.1.1 Tool
- 184.108.40.206 (1) SDK: Tool::Reset, etc.
- 220.127.116.11 (2) SDK: Tool::GetOp
- 18.104.22.168 (3) SDK: LXiTOOLOP_TOOLPIPE, etc. defines
- 22.214.171.124 (4) SDK: LXiTOOLOP_DIFFERENT, etc. defines
- 126.96.36.199 (5) SDK: Tool::CompareOp
- 188.8.131.52 (6) SDK: Tool::UpdateOp
- 184.108.40.206 (7) SDK: LXsTOOL_USETOOLOP define
- 220.127.116.11 (8) PY: empty Tool user class
- 18.104.22.168 (9) SDK: LXi_TASK_SNAP, etc. defines
- 22.214.171.124 (10) SDK: LXs_TASK_SNAP, etc. defines
- 126.96.36.199 (11) SDK: LXs_ORD_WORK, etc. defines
- 188.8.131.52 (12) SDK: LXu_TOOL, etc. defines
- 1.1.1 Tool
- 1.2 ILxTool1 (Legacy Interface)
- 1.2.1 (13) SDK: Tool1::Reset, etc.
- 1.2.2 (14) SDK: LXu_TOOL1, etc. defines
- 1.2.3 Attribute Sequence
- 1.2.4 Tool Operation
- 1.1 COM Interfaces
- 2 ToolVector
- 2.1 (25) SDK: LXsCATEGORY_TOOL define
- 2.2 Standard Tool Packets
- 2.2.1 Subject Packet
- 2.2.2 Action Center Packet
- 2.2.3 Axis
- 2.2.4 Transform Packet
- 2.3 Object Tool Packets
- 2.3.1 (32) SDK: LXsP_TOOL_FALLOFF, etc. defines
- 2.3.2 Falloff Packet Interface
- 2.3.3 Symmetry Packet Interface
- 2.3.4 Subject Packet Interface
- 2.3.5 Texture Packet Interface
- 2.3.6 Element Axis Packet Interface
- 2.3.7 Element Center Packet Interface
- 2.4 Path and Particle Generator Object Packets
- 2.4.1 Path Generator Packet Interface
- 2.4.2 Path Generator: Nodes and their data
- 184.108.40.206 (63) SDK: LXtPathKnot struct
- 220.127.116.11 (64) SDK: LXf_PATHKNOT_BROKEN define
- 18.104.22.168 (65) SDK: PathGeneratorPacket::Count, etc.
- 22.214.171.124 (66) SDK: PathGeneratorPacket::KnotDataSet
- 126.96.36.199 (67) SDK: BagGenerator::Generate, etc.
- 188.8.131.52 (68) SDK: LXu_BAGGENERATOR define
- 184.108.40.206 (69) SDK: empty BagGenerator User Class
- 220.127.116.11 (70) PY: empty BagGenerator user class
- 2.4.3 Path Generator: Walking the Path
- 18.104.22.168 (71) SDK: PathStep::Setup
- 22.214.171.124 (72) SDK: PathStep::Step
- 126.96.36.199 (73) SDK: PathStep::CleanUp
- 188.8.131.52 (74) SDK: LXu_PATHSTEP define
- 184.108.40.206 (75) SDK: empty PathStep User Class
- 220.127.116.11 (76) PY: empty PathStep user class
- 18.104.22.168 (77) SDK: PathGeneratorPacket::Walk
- 22.214.171.124 (78) SDK: LXv_PATHGEN_DIV_COARSE, etc. defines
- 126.96.36.199 (79) SDK: PathGeneratorPacket::Bank
- 188.8.131.52 (80) SDK: LXu_PATHGENERATORPACKET, etc. defines
- 184.108.40.206 (81) SDK: empty PathGeneratorPacket User Class
- 220.127.116.11 (82) PY: empty PathGeneratorPacket user class
- 18.104.22.168 (83) SDK: LXsP_TOOL_PATHGEN define
- 2.4.4 ILxPathStep Wrapper
- 2.4.5 Particle Generator Packet Interface
- 22.214.171.124 (85) SDK: LXtPGenParticle struct
- 126.96.36.199 (86) SDK: LXf_PARTGEN_CONNECT, etc. defines
- 188.8.131.52 (87) SDK: ParticleGeneratorPacket::Count, etc.
- 184.108.40.206 (88) SDK: ParticleGeneratorPacket::InitialParticleSet
- 220.127.116.11 (89) SDK: ParticleGeneratorPacket::HintBoxSet
- 18.104.22.168 (90) SDK: LXu_PARTICLEGENERATORPACKET, etc. defines
- 22.214.171.124 (91) SDK: empty ParticleGeneratorPacket User Class
- 126.96.36.199 (92) PY: empty ParticleGeneratorPacket user class
- 188.8.131.52 (93) SDK: LXsP_TOOL_PARTGEN define
- 2.4.6 ILxParticleGeneratorPacket1
- 2.4.7 Preset Content Packet
- 2.4.8 2D Drawing Style Packet
- 2.4.9 Tool Flags
The primary API for all tools, internal and external, must be the COM ILxTool interface, and the other COM interfaces supported by tools. This assures that external tools are not limited in scope or functionality, and can blend seamlessly into the tool workflow.
The basic interface for tools is ILxTool. This has a set of methods that manage the state of the tool, and query the fundamental tool properties.
|Reset||The Reset method sets the tool attributes back to their initial/default state.|
|Evaluate||This method applys the tool, recursively applying any hierarchy of sub-tools. Naturally, it validates the tool state upon completion.|
|VectorType||This method returns the tool vector type, describing the vector packets required for processing.|
|Order||Specifies the order in the pipe, by returning an Ordinal string.|
|Task||Specifies the type of task performed by the tool.|
|Sequence||This method uses the attribute sequence object given to store the tool's complete state by generating the sequence of attribute changes needed to reproduce that exact state. A tool whose state is expressed entirely by its attributes may return LXe_NOTIMPL from this method, and let the system build the sequence directly from the attribute list.|
(1) SDK: Tool::Reset, etc.
LXxMETHOD( void, Reset) ( LXtObjectID self); LXxMETHOD( void, Evaluate) ( LXtObjectID self, LXtObjectID vts); LXxMETHOD( LXtObjectID, VectorType) ( LXtObjectID self); LXxMETHOD( const char *, Order) ( LXtObjectID self); LXxMETHOD( LXtID4, Task) ( LXtObjectID self); LXxMETHOD( LxResult, Sequence) ( LXtObjectID self, LXtObjectID seq);
It is often desirable to perform incremental updates to meshes, rather than simply evaluating a tool from scratch, every time an attribute changes. This is performed using a tool operation. A tool operation is spawned for every mesh the tool is expected to edit, and is used to perform an initial edit to the mesh. When a tool attribute changes, the tool operation is compared against the current state of the tool. If the tool operation is still valid, it will be updated to use the new tool attributes and re-evaluated to perform an incremental update to the previous evaluation.
Tool Operations also are used in a procedural context. When a tool has been auto converted into a procedural tool item, it's tool operation is evaluated as part of the procedural modeling system to perform initial and incremental edits to a procedural mesh.
This set of functions is used to get the tool op, compare it against tool state and update the tool operation if the tool state is still valid.
|GetOp||The GetOp method is used to spawn a Tool Operation interface that can be used for evaluation and re-evaluation of a mesh edit. The tool is expected to spawn and return a new tool operation every time this function is called. The tool should store any user data in the tool operation before returning. The flags argument is used to pass various flags that specify the context in which the tool is being evaluated; as part of the tool pipe, or procedurally. In future, more flags may be supported.|
(2) SDK: Tool::GetOp
(3) SDK: LXiTOOLOP_TOOLPIPE, etc. defines
|CompareOp||When tool attributes change, a previous tool operation could potentially still be compatible, and could be used to perform incremental updates to a previous evaluation. This function is called to check if a previous tool operation is compatible with the current state of a tool. If it is, then the convert function will be called to update the state of the tool operation, with the latest attributes associated with the tool. The ReEvaluate function on the tool operation will then be called to perform an incremental update to the tool. If the function specifies that the tool operation is incompatible, then the previous result will be discarded, and evaluation will start from scratch with a new tool operation.|
(4) SDK: LXiTOOLOP_DIFFERENT, etc. defines
(5) SDK: Tool::CompareOp
|UpdateOp||If the CompareOp function specifies that a previous tool operation is compatible with the current state of the tool, then this function will be called to copy updated attributes and user data from the tool, to the previous tool operation. The tool operation will then be re-evaluated using this updated data.|
(6) SDK: Tool::UpdateOp
If a tool provides an ILxToolOperation interface, using the GetOp functions. Then it should present the following server tag. This will result in the Tool Operation being used to evaluate the tool. If this server tag is not present, then the standard Evaluate function will be used to evaluate the tool. The value of this tag doesn't matter, the presence of it is enough to signal that a tool operation will be spawned to handle evaluation.
(7) SDK: LXsTOOL_USETOOLOP define
#define LXsTOOL_USETOOLOP "tool.useToolOp"
Empty Tool Python user class.
(8) PY: empty Tool user class
The standard task codes are for: snapping tools, action center and axis, weight (falloff) modification tools, constraint tools, path and particle generators, and the main action tools (like primitives, transforms or mesh edits).
(9) SDK: LXi_TASK_SNAP, etc. defines
#define LXi_TASK_SNAP LXxID4 ('S','N','A','P') #define LXi_TASK_ACEN LXxID4 ('A','C','E','N') #define LXi_TASK_AXIS LXxID4 ('A','X','I','S') #define LXi_TASK_WGHT LXxID4 ('W','G','H','T') #define LXi_TASK_CONS LXxID4 ('C','O','N','S') #define LXi_TASK_ACTR LXxID4 ('A','C','T','R') #define LXi_TASK_SIDE LXxID4 ('S','I','D','E') #define LXi_TASK_PATH LXxID4 ('P','A','T','H') #define LXi_TASK_PTCL LXxID4 ('P','T','C','L') #define LXi_TASK_EFFR LXxID4 ('E','F','F','R') #define LXi_TASK_BRSH LXxID4 ('B','R','S','H') #define LXi_TASK_NOZL LXxID4 ('N','O','Z','L') #define LXi_TASK_PINK LXxID4 ('P','I','N','K') #define LXi_TASK_CONT LXxID4 ('C','O','N','T') #define LXi_TASK_POST LXxID4 ('P','O','S','T') #define LXi_TASK_STYL LXxID4 ('S','T','Y','L') #define LXi_TASK_WORK LXxID4 ('W','O','R','K') #define LXi_TASK_SYMM LXxID4 ('S','Y','M','M')
It's helpful to represent the tool tasks as strings for use in contexts such as procedural modeling.
(10) SDK: LXs_TASK_SNAP, etc. defines
#define LXs_TASK_SNAP "SNAP" #define LXs_TASK_ACEN "ACEN" #define LXs_TASK_AXIS "AXIS" #define LXs_TASK_WGHT "WGHT" #define LXs_TASK_CONS "CONS" #define LXs_TASK_ACTR "ACTR" #define LXs_TASK_SIDE "SIDE" #define LXs_TASK_PATH "PATH" #define LXs_TASK_PTCL "PTCL" #define LXs_TASK_EFFR "EFFR" #define LXs_TASK_BRSH "BRSH" #define LXs_TASK_NOZL "NOZL" #define LXs_TASK_PINK "PINK" #define LXs_TASK_CONT "CONT" #define LXs_TASK_POST "POST" #define LXs_TASK_STYL "STYL" #define LXs_TASK_WORK "WORK" #define LXs_TASK_SYMM "SYMM"
Default ordinals place these kinds of tools into their canonical order. These shouldn't be changed without good reason since new ones can be inserted indefinitely.
(11) SDK: LXs_ORD_WORK, etc. defines
#define LXs_ORD_WORK "\x30" #define LXs_ORD_SYMM "\x31" #define LXs_ORD_CONT "\x38" #define LXs_ORD_STYL "\x39" #define LXs_ORD_SNAP "\x40" #define LXs_ORD_CONS "\x41" #define LXs_ORD_ACEN "\x60" #define LXs_ORD_AXIS "\x70" #define LXs_ORD_PATH "\x80" #define LXs_ORD_WGHT "\x90" #define LXs_ORD_PINK "\xB0" #define LXs_ORD_NOZL "\xB1" #define LXs_ORD_BRSH "\xB2" #define LXs_ORD_PTCL "\xC0" #define LXs_ORD_SIDE "\xD0" #define LXs_ORD_EFFR "\xD8" #define LXs_ORD_ACTR "\xF0" #define LXs_ORD_POST "\xF1"
The ILxTool Interface is accessed via the LXu_TOOL unique ID, or its human-readable alias, LXa_TOOL.
(12) SDK: LXu_TOOL, etc. defines
ILxTool1 (Legacy Interface)
This interface was retired in modo 901, and was replaced with an updated one that adds a few more methods.
(13) SDK: Tool1::Reset, etc.
LXxMETHOD( void, Reset) ( LXtObjectID self); LXxMETHOD( void, Evaluate) ( LXtObjectID self, LXtObjectID vts); LXxMETHOD( LXtObjectID, VectorType) ( LXtObjectID self); LXxMETHOD( const char *, Order) ( LXtObjectID self); LXxMETHOD( LXtID4, Task) ( LXtObjectID self); LXxMETHOD( LxResult, Sequence) ( LXtObjectID self, LXtObjectID seq); LXxMETHOD( int, ShouldBeAttribute) ( LXtObjectID self, LXtID4 task);
(14) SDK: LXu_TOOL1, etc. defines
The ILxAttrSequence interface is intended to complement attribute lists by capturing the sequence of attribute edits required to create a specific state within an object which implements the ILxAttributes interface. An attribute list is a minimal snapshot of an object's exposed data, which may not fully describe the internal state of the object. This would be the case if attribute changes had a cumulative effect on the object (e.g. adding elements to a list). Preserving this state is accomplished by using the ILxAttrSequence interface to 'record' the necessary attribute changes for some host, which can then regenerate the object state by 'playing back' the edits.
|Integer||Use this method to record a change to an integer type attribute by specifying the attribute name and the new value.|
|Float||Use this method to record a change to an floating point attribute (a double).|
|String||Use this method to record a change to an string attribute.|
|Value||Use this method to record a change to an attribute using a generic ILxValue.|
(15) SDK: AttrSequence::Integer, etc.
LXxMETHOD( LxResult, Integer) ( LXtObjectID self, const char *name, int value); LXxMETHOD( LxResult, Float) ( LXtObjectID self, const char *name, double value); LXxMETHOD( LxResult, String) ( LXtObjectID self, const char *name, const char *value); LXxMETHOD( LxResult, Value) ( LXtObjectID self, const char *name, LXtObjectID value);
Empty AttrSequence Python user class.
(16) PY: empty AttrSequence user class
The ILxAttrSequence Interface is accessed via the LXu_ATTRSEQUENCE unique ID.
(17) SDK: LXu_ATTRSEQUENCE define
#define LXu_ATTRSEQUENCE "F54FEF16-223F-439D-8593-6F350783993E"
(18) SDK: empty AttrSequence User Class
A Tool Operation is a special interface that allows tools to be incrementally evaluated. The tool spawns and returns a Tool Operation interface. This tool operation interface is then used for evaluation and re-evaluation of the tool.
|Evaluate||Once a tool has spawned a tool operation, this function will be called to perform an initial evaluation.|
(19) SDK: ToolOperation::Evaluate
|ReEvaluate||Subsequent evaluations of the tool operation will be performed using the ReEvaluate function. The tool will test the tool operation to see if it is still compatible. If it is, it's state will be updated and then ReEvaluate will be called to perform an incremental update.|
(20) SDK: ToolOperation::ReEvaluate
|Blend||The Blend function is used to map elements generated by one actor tool operation to elements generated by another. A second tool operation is provided with alternate settings, along with an ILxToolOperation object, which can be used for marking two corresponding elements as equivalent.|
(21) SDK: ToolOperation::Blend
(22) SDK: LXu_TOOLOPERATION, etc. defines
(23) SDK: empty ToolOperation User Class
Empty Tool Operation Python user class.
(24) PY: empty ToolOperation user class
The evaluation/execution of the tool pipeline uses a GenVector-like paradigm in which the elements all declare what packets they need to read and alter. The combined result of all these packets is a ToolVector, which is evaluated to operate the tool.
(25) SDK: LXsCATEGORY_TOOL define
#define LXsCATEGORY_TOOL "tool"
Standard Tool Packets
We define here some of the most standard tool packets.
The subject packet as a mesh, a vmap and the selection type to operate on.
(26) SDK: LXpToolSubject struct
LXtMeshID mesh; LXtMeshMapID vmap; LXtID4 type; LXtMeshID base;
Action Center Packet
The action center will be mostly used by transform tools like scale and rotate. The packet is set by action center tools, like the mouse (Auto) action center tool which converts the 2D position into a 3D position.
(27) SDK: LXpToolActionCenter struct
This packet is set by axis tools, like the Auto-Axis tool which sets the axis using a principal axis chosen by the event translation object. The axis is a unit vector which will often be along a principal axis. In this case, the 'axIndex' will have the index for that axis. Otherwise, axIndex will be -1. The axIndex should be treated as a hint, so a tool setting this packet should assure that a correct axis vector is set even if a principal axis is selected and the index is set. A tool reading this packet should be prepared to use the axis vector, since the index may be set to -1 even though the vector happens to lie along a principal direction. The axis vector is also the 'forward' vector. The 'up' vector is a unit vector perpendicular to the axis, which is nominally in the 'up' direction. The 'right' vector is the last vector to form the basis. The 'm' matrix is the matrix formed by the 3 basis vectors and 'mInv' is its inverse.
(28) SDK: LXpToolAxis struct
Tools may be transformed by other tools. For instance, a construction plane tool will apply the plane's transformation to the following tools in the pipe. The construction plane tool can do that by setting the Xfrm packet matrix and position vector. Tools which set this packet may provide an inverse transform matrix, to save redundant or more difficult inversions downstream.
(29) SDK: LXpToolXfrm struct
LXtVector v; LXtMatrix m; LXtMatrix mInv; int flags; int handedness; unsigned int marks;
The Xfrm packet flags can provide hints to tools about the state of the transform. LXiTVXFMf_OFFSET should be set if the position vector 'v' is non-zero. LXiTVXFMf_MATRIX should be set if the matrix is NOT the identity matrix, as an indication to tools that this transformation is necessary. LXiTVXFMf_INVERSE should be set if there is a valid inverse transform matrix in 'mInv'. Transforms that have no bits from LXiTVXFMf_USEFUL set are identity transformations, and can be skipped.
(30) SDK: LXiTVXFMf_OFFSET, etc. defines
(31) SDK: LXsP_TOOL_SUBJECT, etc. defines
Object Tool Packets
(32) SDK: LXsP_TOOL_FALLOFF, etc. defines
Falloff Packet Interface
The falloff packet is set by falloff tools. It is a COM object with the ILxToolFalloff interface.
(33) SDK: FalloffPacket::Evaluate
(34) SDK: FalloffPacket::Screen
(35) SDK: LXu_FALLOFFPACKET define
#define LXu_FALLOFFPACKET "D0F8CF5D-1BB5-4002-810B-0E7EF34B7867"
(36) SDK: empty FalloffPacket User Class
Empty FalloffPacket Python user class.
(37) PY: empty FalloffPacket user class
Symmetry Packet Interface
The symmetry packet provides interfaces to tools about the state of the symmetry.
|Active||This function returns the activity of the symmetry.|
|Axis||This function fills the axis vector of the symmetry and the offset value, and it returns the axis number (0-2) for XYZ, otherwise 3 for arbitrary axis.|
|Point||This function returns the symmetric vertex for the given vertex. If there is none, null is returned.|
|Polygon||This function returns the symmetric polygon for the given polygon. If there is none, null is returned.|
|Edge||This function returns the symmetric edge for the given edge. If there is none, null is returned.|
|Position||This function takes any position and fills the symmetric position. If the position is on the symmetric plane, it returns zero, otherwise nonzero.|
(38) SDK: SymmetryPacket::Active, etc.
LXxMETHOD( int, Active) ( LXtObjectID self); LXxMETHOD( int, Axis) ( LXtObjectID self, LXtFVector axvec, float *offset); LXxMETHOD( LXtPointID, Point) ( LXtObjectID self, LXtMeshID mesh, LXtPointID vrx); LXxMETHOD( LXtPolygonID, Polygon) ( LXtObjectID self, LXtMeshID mesh, LXtPolygonID pol); LXxMETHOD( LXtEdgeID, Edge) ( LXtObjectID self, LXtMeshID mesh, LXtEdgeID edge); LXxMETHOD( int, Position) ( LXtObjectID self, const LXtFVector pos, LXtFVector sv); LXxMETHOD( int, BaseSide) ( LXtObjectID self); LXxMETHOD( void, SetBase) ( LXtObjectID self, const LXtFVector pos); LXxMETHOD( int, TestSide) ( LXtObjectID self, const LXtFVector pos, int useBase);
(39) SDK: LXu_SYMMETRYPACKET define
#define LXu_SYMMETRYPACKET "F13F6933-1289-4EFC-9CE1-D5C4F13EE7D8"
(40) SDK: empty SymmetryPacket User Class
Empty SymmetryPacket Python user class.
(41) PY: empty SymmetryPacket user class
Subject Packet Interface
The subject packet provides a wrapper around the layer service, allowing a layer scan object to be allocated for accessing geometry.
|ScanAllocate||This function allocates a layer scan object, which can be used for accessing and enumerating meshes in the scene. The flags passed to the flag argument should be the same as the flags passed to the ScanAllocate function in the Layer Service.|
|Type||This function returns the current selection type.|
(42) SDK: Subject2Packet::ScanAllocate
(43) SDK: Subject2Packet::Type
(44) SDK: LXu_SUBJECT2PACKET define
#define LXu_SUBJECT2PACKET "CA342D92-26C8-4A25-AD27-0163AD54730D"
(45) SDK: CLxUser_Subject2Packet::BeginScan method
Empty Subject2Packet Python user class.
(46) PY: empty Subject2Packet user class
Texture Packet Interface
The texture packet is similar to the falloff packet. It does essentially the same thing which is to compute a value given a 3D position/mesh elemement. The difference with the falloff packet is that the texture packet may compute different data types: scalar, color or vectors, unlike the falloff function which only returns scalar values.
(47) SDK: TexturePacket::Evaluate
(48) SDK: LXu_TEXTUREPACKET define
#define LXu_TEXTUREPACKET "851271E5-F4F4-444D-A87A-563B9E1E6EFB"
(49) SDK: empty TexturePacket User Class
Empty TexturePacket Python user class.
(50) PY: empty TexturePacket user class
Element Axis Packet Interface
Elements are groups of vertices (or polygons) linked by virtue of their interconnections. The element axis packet has one method to compute the local axis given the mesh and one vertex in the element. For faster updates, the method also precomputes the direct and inverse transformation matrices.
(51) SDK: ElementAxisPacket::Axis
(52) SDK: LXu_ELEMENTAXISPACKET define
#define LXu_ELEMENTAXISPACKET "292A47BF-3CF5-492D-AAFD-AE761092A782"
(53) SDK: empty ElementAxisPacket User Class
Empty ElementAxisPacket Python user class.
(54) PY: empty ElementAxisPacket user class
Element Center Packet Interface
Likewise, the element center packet compute the element center given the mesh and a vertex in the element.
(55) SDK: ElementCenterPacket::Center
(56) SDK: LXu_ELEMENTCENTERPACKET define
#define LXu_ELEMENTCENTERPACKET "5221C415-073A-4610-BCB6-F820F8D7F6D0"
(57) SDK: empty ElementCenterPacket User Class
Empty ElementCenterPacket Python user class.
(58) PY: empty ElementCenterPacket user class
Path and Particle Generator Object Packets
Generators are object packets which produce and manage data expressed by downstream Effector tools. At the moment there are two classes of generators, Path Generators and Particle Generators. Path Generators generally maintain and edit some parametrized 3D trajectory, while Particle Generators produce a list of discrete state-vectors algorithmically. Paths are sets of connected segments forming a continuous curve through 3D space, particles are discrete sets of values located and oriented in 3D space. A particle generator can easily be created by sampling a continuous path, but the converse is not necessarily true, as continuity of tangents is not guaranteed for the path.
Path Generator Packet Interface
A path generator packet delivers access to a continuous path through 3D space defined by a parametric curve. For some paths, the tangents may not be continuous.
The curve implementation is not exposed. Instead the position in 3D along the path at a given parameter value is returned by the "Value" method.
(59) SDK: PathGeneratorPacket::Value
|Value||Evaluates curve at parameter value 't' (0 <= t <= 1), putting the results in 'pos'.|
It is often useful to get things like the path length, or the tangent at a given point. Since some implementations can deliver these quantities without doing annoying numerical derivatives (or integrals?), the path packet will handle these calculations internally, and provide simple access.
(60) SDK: PathGeneratorPacket::Length
(61) SDK: PathGeneratorPacket::Tangent
(62) SDK: PathGeneratorPacket::Source
|Length||Returns the path length from parameter t=0 to the given t (<1).|
|Tangent||Returns the tangent vector at the given parameter value. For uninitialized or zero-length curves, this function returns an LXe_OUTOFBOUNDS error, making it a useful way for the object to dcelare, and for a client to check if the curve is valid.|
|Source||Returns the source polygon for the path.|
Path Generator: Nodes and their data
Most paths are defined by a series of control points (knots). These knots are characterized by a position, a parameter value on the path, some tangents, and flags which tell, among other things, wether the tangents are continuous. It is expected that all discontinuities in a path are represented by knots.
(63) SDK: LXtPathKnot struct
The flags determine if the tangents are equal or not.
(64) SDK: LXf_PATHKNOT_BROKEN define
#define LXf_PATHKNOT_BROKEN 1
(65) SDK: PathGeneratorPacket::Count, etc.
|Count||Returns the number of nodes in the path. It will return 0 for an uninitialized or empty sequence, or a synthetic, continuous path which happens to have no nodes. A synthetic path with discontuities should have the courtesy to mark them with nodes.|
|Knot||Fills in the LXtPathKnot for the knot at 'index'.|
|Current||Returns the index of the 'current' knot, or -1 if there is none. This will allow downstream tools to build lists of extra per-knot data, and display/edit the appropriate values in the UI.|
For many applications, a downstream client tool of the path generator will want to attach some data to the each knot. Because the knots are created and destroyed by undoable actions, maintaining that data would be difficult for a client. Adding an optional client-defined bit of encapsulated data (baggage) should help. The interface for this is the ILxBagGenerator which clients will provide to create, copy and release their custom data.
(66) SDK: PathGeneratorPacket::KnotDataSet
|KnotDataSet||This function sets the optional per-knot data generator. Use it to set the value of the LXtPathKnot clientData element.|
The Bag generator interface is a simple way for clients to attach data to dynamic objects like path nodes. The 'bag' pointer returned by Generate() should be passed to Dispose() when it is no longer needed.
(67) SDK: BagGenerator::Generate, etc.
|Generate||This method allocates new client data. For convenience some node-specific data may be passed in to the generator. If the cloneMe pointer is non-NULL, it is assumed to point to suitable client data, and it will be copied into the new bag exactly.|
|Dispose||This frees the bag and its contents.|
(68) SDK: LXu_BAGGENERATOR define
#define LXu_BAGGENERATOR "9A368FAA-7576-42B9-9B6A-C2F8D34612F0"
(69) SDK: empty BagGenerator User Class
Empty BagGenerator Python user class.
(70) PY: empty BagGenerator user class
Path Generator: Walking the Path
In many cases, travelling the along path can also be done more efficiently internally. The Path Generator thus provides a method for scanning the entire curve with a client-supplied ILxPathStep.
(71) SDK: PathStep::Setup
The step function can end the walk at any time by returning a non-zero value.
(72) SDK: PathStep::Step
(73) SDK: PathStep::CleanUp
(74) SDK: LXu_PATHSTEP define
#define LXu_PATHSTEP "B9F58563-FBA0-4CA2-866B-1DD64174A277"
(75) SDK: empty PathStep User Class
Empty PathStep Python user class.
(76) PY: empty PathStep user class
(77) SDK: PathGeneratorPacket::Walk
|Walk||This function 'walks' along the path, invoking the supplied ILxPathStep's step() at each step with the curve parameter and the 3D position. It returns the number of steps taken, which is determined by the angle argument. The angle (in radians) is the maximum angle allowed between adjacent linear divisions. For convenience, Coarse, Medium, and Fine presets (corresponding to 6, 5, and 3 degrees, respectively) are defined.|
(78) SDK: LXv_PATHGEN_DIV_COARSE, etc. defines
(79) SDK: PathGeneratorPacket::Bank
|Bank||Returns the bank angle at the given parameter value.|
(80) SDK: LXu_PATHGENERATORPACKET, etc. defines
(81) SDK: empty PathGeneratorPacket User Class
Empty PathGeneratorPacket Python user class.
(82) PY: empty PathGeneratorPacket user class
(83) SDK: LXsP_TOOL_PATHGEN define
#define LXsP_TOOL_PATHGEN "tool.pathGenerator"
For convenience, a basic implementation of the ILxPathStep interface is provided. It will call a client callback at each step. The callback must be in this not unfamiliar form:
(84) SDK: PathWalkerFunc typedef
typedef void PathWalkerFunc (void *data, double t, LXtVector pos);
Particle Generator Packet Interface
A particle generator object manages an ordered sequence of particles, or transforms, each defined by its own position, rotation and scale. While the scale and orientation could be combined in a single matrix, they will be preserved separately for the convenience of working with orthonormal matrices. A
(85) SDK: LXtPGenParticle struct
|position||Particle position in space|
|scale||A vector of scaling factors for each of the particle coordinates|
|orientation||The particle coordinate system, defined by an orthonormal transformation matrix.|
|flags||The 'connect' flag tells clients that the particle is part of a continuous series by indicating that this particle is connected to the one following it. If this is the last particle, it is this flag means that the particle is connected to the first, closing the sequence. The 'absSize' flag tells clients that the particle size is absolute. In many cases the size is relative, depending on what the effector is dealing with. The 'mirror' flag is a special mode to make mirrored particles based on the scale vectors. "curve" flag is set by curve like generator which requires a duplication at the initial particle position.|
(86) SDK: LXf_PARTGEN_CONNECT, etc. defines
(87) SDK: ParticleGeneratorPacket::Count, etc.
|Count||Returns the number of particles in the sequence. It will return 0 for an uninitialized or empty sequence, or 1 if only the InitialParticleSet method has been used to set initial conditions for the generator.|
|Particle||Fills in the LXtPGenParticleID for the particle at 'index'.|
The generator has to be responsive to the requirements of the effector. For example, the sweep effector which is the "bit" for the lathe and extrude tool composites has to be able to provide the generator with a start location. This allows the radial generator to put its first particle at the location of the source data, and have the other particles spiral out from there.
(88) SDK: ParticleGeneratorPacket::InitialParticleSet
(89) SDK: ParticleGeneratorPacket::HintBoxSet
|InitialParticleSet||Set the initial state of the particle generator. The state of particle supplied will be copied and used as the 0th particle.|
|HintBoxSet||This is an optional method for InitialParticleSet. Set the bounding box and the initial orientation when it defines the initial particle.|
|InitialParticleSetFromMesh||Set the initial state of the particle generator. The state of particle supplied will be copied and used as the 0th particle. This version will use the supplied mesh instead of scanning global layers.|
(90) SDK: LXu_PARTICLEGENERATORPACKET, etc. defines
(91) SDK: empty ParticleGeneratorPacket User Class
Empty ParticleGeneratorPacket Python user class.
(92) PY: empty ParticleGeneratorPacket user class
(93) SDK: LXsP_TOOL_PARTGEN define
#define LXsP_TOOL_PARTGEN "tool.partGenerator"
This packet interface has been deprecated and replaced by ILxParticleGeneratorPacket.
(94) SDK: ParticleGeneratorPacket1::Count, etc.
LXxMETHOD( int, Count) ( LXtObjectID self, LXtObjectID vts); LXxMETHOD( LxResult, Particle) ( LXtObjectID self, LXtObjectID vts, int index, LXtPGenParticle *part); LXxMETHOD( LxResult, InitialParticleSet) ( LXtObjectID self, const LXtPGenParticle *part); LXxMETHOD( LxResult, HintBoxSet) ( LXtObjectID self, const LXtBBox *box, const LXtPGenParticle *part);
(95) SDK: LXu_PARTICLEGENERATORPACKET1, etc. defines
Preset Content Packet
The Preset Content Packet holds the name, type and commonly used attributes for content preset files. It should be written to be TASK_CONT type tools, and read-only for tools downstream. The flags are used for boolean attributes, and may be interpreted differently for each type of content.
(96) SDK: LXpToolContent struct
const char *path; const char *type; double scale; LXtVector axis; LXtVector offset; int axIndex; int flags; void *data; /* * Temporary changes to ensure the content browser works correctly when running as a toolop. * We cannot store pointers to strings owned by toolops in the same way we would for non-procedural tools. * because the toolop data is not guaranteed to still exist when the packet is read by the next tool. * We should replace this structure with a COM object as soon as possible. */ char pathBuffer; char typeBuffer;
(97) SDK: LXsP_TOOL_CONTENT define
#define LXsP_TOOL_CONTENT "tool.content"
2D Drawing Style Packet
This packet holds common style attributes for vector composition elements.
(98) SDK: LXpToolStyle struct
(99) SDK: LXsP_TOOL_STYLE define
#define LXsP_TOOL_STYLE "tool.style"
Tool flags are used for the enable, visibility and hauling states. Additional bits describe a tool which will be automatically activated.
(100) SDK: LXf_TOOL_ENABLE, etc. defines
#define LXf_TOOL_ENABLE 1 #define LXf_TOOL_ACTIVE 2 #define LXf_TOOL_HAUL 4 #define LXf_TOOL_HAUL2 (1<<16) + LXf_TOOL_HAUL #define LXf_TOOL_NOHAUL (1<<17) #define LXf_TOOL_AUTOACT (1<<4) #define LXf_TOOL_IMPLICIT (1<<5) #define LXf_TOOL_POSTAPPLY (1<<6) #define LXf_TOOL_NOCACHE (1<<7) #define LXf_TOOL_IMMEDIATE (1<<8) #define LXf_TOOL_NOATTRS (1<<9) #define LXf_TOOL_STAYACTIVE (1<<10) #define LXf_TOOL_INDIRECT (1<<11) #define LXf_TOOL_DRAW_MASK (0xFF<<24) #define LXx_TOOL_DRAWFLAGS(f) ((f)>>24) #define LXx_TOOL_SETDRAW(f) ((f)<<24) #define LXm_TOOL_TRANSIENT (LXf_TOOL_HAUL|LXf_TOOL_HAUL2) #define LXm_TOOL_STATIC (~(LXf_TOOL_ACTIVE | LXf_TOOL_IMPLICIT | LXm_TOOL_TRANSIENT)) #define LXm_TOOL_DEFAULT (LXf_TOOL_ENABLE | LXf_TOOL_VISIBLE)
|LXf_TOOLf_ENABLE||Tool enabled state|
|LXf_TOOLf_ACTIVE||Tool has been activated for interactive processing.|
|LXf_TOOLf_HAUL||Tool receives primary hauling input.|
|LXf_TOOLf_HAUL2||Tool receives secondary hauling input.|
|LXf_TOOLf_AUTOACT||Tool activates upon insertion into toolpipe.|
|LXf_TOOLf_IMPLICIT||Tool was activated indirectly as a result of downstream tool activation, and has not been modified manually by the user.|
|LXf_TOOLf_POSTAPPLY||Tool suggests 'Post-Apply' mode, which defers mesh operations until interactive tool use is completed.|
|LXf_TOOLf_NOCACHE||Tool should not be cached with user-adjustments, i.e. it is locked.|
|LXm_TOOLm_TRANSIENT||Tool node flags are stored in presets, but some of the bit are transient, and should not be preserved/restored as part of the preset properties. This mask defnes those bits.|
|LXf_TOOLf_IMMEDIATE||The tool should deactivate upon mouse-up, disallowing further edits.|
|LXf_TOOLf_NOATTRS||The tool should not save any state (attributes) in presets. This includes any Attr. sequence. Tools with this flag will load into the pipeline with just the default attribute values the tool creates.|
|LXf_TOOLf_NOHAUL||The tool should not handle hauling events, allowing selection. This would be countermanded by a ToolModel flag (NEEDSHAUL) specifying that a tool has no handles and thus requires hauling, forbidding the use of selection while the tool is active.|
|LXf_TOOLf_STAYACTIVE||The tool should not deactivate once it has been activated, this can be useful when used in conjunction with TOOLf_IMMEDIATE as it allows keeping a tool active when the pipe auto deactivates.|
|LXf_TOOLf_INDIRECT||The tool is always activated indirectly as a result of downstream tool activation.|
The draw flags are defined more precisely. They are used by the ToolModel interface extensively, but the tool pipe will still benefit from understanding the combination of these bits which determine a tool's visibility.
(101) SDK: LXf_TOOL_DRAW_PLAIN, etc. defines
#define LXf_TOOL_DRAW_PLAIN (1<<24) #define LXf_TOOL_DRAW_FANCY (2<<24) #define LXf_TOOL_DRAW_PLAIN_S (LXf_TOOL_DRAW_PLAIN<<4) #define LXf_TOOL_DRAW_FANCY_S (LXf_TOOL_DRAW_FANCY<<4) #define LXf_TOOL_VISIBLE (LXf_TOOL_DRAW_PLAIN | LXf_TOOL_DRAW_FANCY | LXf_TOOL_DRAW_PLAIN_S | LXf_TOOL_DRAW_FANCY_S) #define LXf_TOOL_PLAIN (LXf_TOOL_DRAW_PLAIN|LXf_TOOL_DRAW_PLAIN_S) #define LXf_TOOL_FANCY (LXf_TOOL_DRAW_FANCY|LXf_TOOL_DRAW_FANCY_S)
|LXf_TOOLf_DRAW_MASK||These bits are set to pass through (after shifting) to the ToolModel draw() and test() functions.|
|LXf_TOOLf_VISIBLE||Tool is drawn.|