CATIA Macro Development Assistant

Problem It Solves

CATIA V5/V6 macros are often hard to maintain because CATScript, VBScript, and VBA have different syntax limits, and CATIA automation interfaces are large and framework-specific. Small details such as collection iteration, error handling, string formatting, and drawing coordinate behavior can fail only at runtime.

How The Skill Works

This skill defaults to CATScript and generates code that avoids known engine failures:

• Default target: prefer CATScript unless VBScript or VBA is explicitly required.
• Hard-limit checks: avoid cross-block GoTo, For Each over CATIA collections, Next i, Format(), typed Dim, and On Error GoTo label.
• API lookup: locate interfaces in references/interfaces/ by interface_, method name, or framework file.
• Example reuse: adapt Drafting and 2D Layout examples from references/macros/_all_examples.txt.

Boundaries And Caveats

Use it for automating drawing views, dimensions, tables, and component instantiation. Note that CATIA object behavior can differ from general VBScript assumptions: DrawingComponent.GetRealColor() is unreliable, paper dimensions should be read at runtime, and view coordinates must include Component.x and Component.y for absolute sheet position.