Manufacturing DevBlog

Autodesk Manufacturing DevCamp material

We’ve posted the material from the recent MFG DevCamp 2012 to the following locations:-

• ADN extranet >> Events >> Autodesk DevCamps 2012 (ADN members only access)
• Autodesk Developer Network Open site >> API Training Archive section (public)

These links provide one zip for the ease of download. Classes are divided in five tracks:

1. Autodesk Inventor App Development for Beginners
2. Autodesk Inventor App Development for Experts
3. Autodesk PLM
4. Cloud and Mobile Technologies
5. (a) Business Development (b) Autodesk Engineer To Order (ETO)

 

Thanks to those who both presented classes, and those who attended the event. It was great meeting everyone in person, and very interesting hearing about all the interesting projects so many of you are involved with.

Change the Width and Height of a Sheet by Inventor API

By Barbara Han

To set a sheet to a specific width and height, directly writing the width and height property of the sheet will not work if you don’t specify the size property kCustomDrawingSheetSize from DrawingSheetSizeEnum in advance.

Here is a VB.NET sample code demonstrating how to do that:

Sub setSheetSize()
        Dim st As Sheet
        Dim dw As DrawingDocument
        dw = Thisapplication.ActiveDocument

        st = dw.ActiveSheet
        Dim w As Double
        w = st.Width / 2

        Dim h As Double
        h = st.Height / 2

        st.Size = DrawingSheetSizeEnum.kCustomDrawingSheetSize

        st.Height = h
        st.Width = w
    End Sub

_COM_SMARTPTR_TYPEDEF declaration problem with #import

By Philippe Leefsma

Q:

In the RxInventor.tlh the definition of some named interface object are declared like this:
   _COM_SMARTPTR_TYPEDEF(GenericObject, __uuidof(IDispatch));
It is clear the IDispatch UUID is not one of the interface. This cause a lot of problem in our code.

Can you explain this?

A:

The problem with the smart pointer typedef generation is a problem with Microsoft's implementation of #import and there is nothing we can do about it. All of Inventor's IDispatch supporting interfaces are dispinterfaces, not dual interfaces like AutoCAD's. #import appears to only use the strong IID when the interface is a vtable or a dual. #import puts on dispinterfaces, and uses IDispatch as the interface IID.

This is just another of several reasons to avoid the _com_ptr_t smart pointers, especially since #import only half declares them. It is recommended to stick with CCom(QI)Ptr or CComPtr<> template class, since you will specify the right interface uuid.

Adding Dropdown/popup buton in inventor ribbon panel

By Philippe Leefsma

Q:

I want to create dropdown and popup controls in Inventor ribbon interface, like for example the "Text" command button in the Sketch -> Draw panel, and the "UserInterface" command button in the View tab in the Part.

A:

You should use CommandControls.AddButtonPopup method, and CommandControls.AddTogglePopup method respectively in order to add those two styles of controls in the ribbon panel. The attached .Net add-in contains an example for both.

Ribbon Sample

Get the Display Value of the Parameter in Inventor

By Barbara Han

Issue

Parameter object has ModelValue, and Value properties, but they return the evaluation of the parameter in database units. Expression property returns a string including display unit, for example "10 mm", but what I want is just "10". Please suggest the way for getting the evaluation of the parameter in drawing display unit when you don't know what database unit this parameter uses.

Solution

UnitsOfMeasure.ConvertUnits() method can convert a value from one unit to another. Here is a sample to call ConvertUnits:

displayVaule = UOM.ConvertUnits(parameter1.Value, UnitsTypeEnum.kDatabaseLengthUnits, UnitsTypeEnum.kDefaultDisplayLengthUnits)

If you don't know which database unit to use, you can call GetDatabaseUnitsFromExpression method to get the database unit string, then call GetTypeFromString method to convert the string to UnitsTypeEnum value. Below is the VB.NET sample code that does it:

Sub parameterInfo()

  Dim oDoc As PartDocument

  oDoc = ThisApplication.ActiveDocument

  Dim para As Parameter

  Dim UOM As UnitsOfMeasure

  UOM = oDoc.UnitsOfMeasure

  For Each para In oDoc.ComponentDefinition.Parameters

    Debug.Print("Expression is " + para.Expression)

    Debug.Print("Display unit is " + para.Units)

    Debug.Print("ModelVaule is " + para.ModelValue.ToString)

    Debug.Print("Value is " + para.Value.ToString)

    Dim displayValue As String

 

    displayValue = UOM.ConvertUnits(para.Value, _

                    UOM.GetTypeFromString(UOM.GetDatabaseUnitsFromExpression( _

                    para.Expression, para.Units)), _

                    para.Units)

 

    Debug.Print("Display value is " + displayValue)

  Next

End Sub

Below is a sample output:

Expression is 1.105 in
Display unit is in
ModelVaule is 2.80629415684689
Value is 2.80629415684689
Display value is 1.10484021923106

Embedding a WPF User Control in a DockableWindow in Inventor

By Barbara Han

If you have a Windows Form containing an ElementHost control and the ElementHost containing a WPF UserControl, then assign this form as a child of a DockableWindow, you can get a dockable window that shows WPF control in Inventor.

The following is main VB.NET code snippet:

StandardAddInServer.vb:

Imports Inventor

Imports System.Runtime.InteropServices

Imports Microsoft.Win32

Imports System.Windows.Forms

 

Namespace vbButton

  <ProgIdAttribute("vbButton.StandardAddInServer"), _

  GuidAttribute("f00de0d0-9de0-46fb-ac94-4e6f8633bbaa")> _

  Public Class StandardAddInServer

    Implements Inventor.ApplicationAddInServer

 

    ' Inventor application object.

    Private m_inApp As Inventor.Application

 

    Private myButtonDef As ButtonDefinition

    Private Dim addInCLSIDString As String

 

#Region "ApplicationAddInServer Members"

 

    Public Sub Activate(ByVal addInSiteObject As Inventor.ApplicationAddInSite, ByVal firstTime As Boolean) Implements Inventor.ApplicationAddInServer.Activate

 

      ' This method is called by Inventor when it loads the AddIn.

      ' The AddInSiteObject provides access to the Inventor Application object.

      ' The FirstTime flag indicates if the AddIn is loaded for the first time.

 

      ' TODO:  Add ApplicationAddInServer.Activate implementation.

      ' e.g. event initialization, command creation etc.

      m_inApp = addInSiteObject.Application

 

      ' Retrieve the GUID of this class for later use

 

      Dim addInCLS As GuidAttribute

      addInCLS = CType(System.Attribute.GetCustomAttribute(GetType(StandardAddInServer), _

           GetType(GuidAttribute)), GuidAttribute)

      addInCLSIDString= "{" & addInCLS.Value & "}"

 

      ' Create the button definition objects

 

      Dim smallIcon As System.Drawing.Icon

      smallIcon = New System.Drawing.Icon(My.Resources.MyCommand1Icon, 16, 16)

      Dim largeIcon As System.Drawing.Icon

      largeIcon = New System.Drawing.Icon(My.Resources.MyCommand1Icon, 32, 32)

 

      Dim smallPic As IPictureDisp

      smallPic = Microsoft.VisualBasic.Compatibility.VB6.IconToIPicture(smallIcon)

      Dim largePic As IPictureDisp

      largePic = Microsoft.VisualBasic.Compatibility.VB6.IconToIPicture(largeIcon)

 

      myButtonDef = m_inApp.CommandManager.ControlDefinitions.AddButtonDefinition( _

          "Test", "vbButton:Btn1", _

          CommandTypesEnum.kShapeEditCmdType, _

          addInCLSIDString, "test", _

          "", smallPic, largePic)

 

      ' Link the button objects with the event

 

      AddHandler myButtonDef.OnExecute, AddressOf MyButtonDefinition_OnExecute

 

      ' Start UI customization:

 

      If firstTime = True Then

 

        ' Access user interface manager

 

        Dim uiManager As UserInterfaceManager

        uiManager = m_inApp.UserInterfaceManager

 

        Dim interfaceStyle As InterfaceStyleEnum

        interfaceStyle = uiManager.InterfaceStyle

 

        If interfaceStyle = InterfaceStyleEnum.kRibbonInterface Then

 

          ' Create our commands in ribbon interface

 

          Dim ribbons As Ribbons

          ribbons = uiManager.Ribbons

 

          ' Assembly: add our commands in Assembly environment

 

          Dim myRibbon As Ribbon

          myRibbon = ribbons.Item("ZeroDoc")

 

          ' Get the tabs associated ribbon

 

          Dim ribbonTabs As RibbonTabs

          ribbonTabs = myRibbon.RibbonTabs

          Dim myTab As RibbonTab

          myTab = ribbonTabs.Add("MyAddIn", "vbButton:ButtonTab1", _

            addInCLSIDString, "")

 

          ' Create a new panel within our new tab

 

          Dim ribbonPanels As RibbonPanels

          ribbonPanels = myTab.RibbonPanels

          Dim myPanel As RibbonPanel

          myPanel = ribbonPanels.Add("My Panel", _

          "vbButton:myPanel1", addInCLSIDString, "", False)

 

          ' Add two commands to the Clone panel

 

          Dim myPanelCtrls As CommandControls

          myPanelCtrls = myPanel.CommandControls

 

          Dim myCloneBtnCmdCtrl As CommandControl

          myCloneBtnCmdCtrl = myPanelCtrls.AddButton(myButtonDef, True, True, "", False)

        End If

      End If

 

      ' End UI customization.

    End Sub

    Private Sub MyButtonDefinition_OnExecute(ByVal Context As Inventor.NameValueMap)

      Dim f As Form1 = New Form1(m_inApp, addInCLSIDString)

      f.ShowDialog()

    End Sub

 

    Public Sub Deactivate() Implements Inventor.ApplicationAddInServer.Deactivate

 

      ' This method is called by Inventor when the AddIn is unloaded.

      ' The AddIn will be unloaded either manually by the user or

      ' when the Inventor session is terminated.

 

      ' TODO:  Add ApplicationAddInServer.Deactivate implementation

 

      ' Release objects.

      Marshal.ReleaseComObject(m_inApp)

      m_inApp = Nothing

      RemoveHandler myButtonDef.OnExecute, AddressOf MyButtonDefinition_OnExecute

      Marshal.ReleaseComObject(myButtonDef)

      myButtonDef = Nothing

      System.GC.WaitForPendingFinalizers()

      System.GC.Collect()

 

    End Sub

 

    Public ReadOnly Property Automation() As Object Implements Inventor.ApplicationAddInServer.Automation

 

      ' This property is provided to allow the AddIn to expose an API

      ' of its own to other programs. Typically, this  would be done by

      ' implementing the AddIn's API interface in a class and returning

      ' that class object through this property.

 

      Get

        Return Nothing

      End Get

 

    End Property

 

    Public Sub ExecuteCommand(ByVal commandID As Integer) Implements Inventor.ApplicationAddInServer.ExecuteCommand

 

      ' Note:this method is now obsolete, you should use the

      ' ControlDefinition functionality for implementing commands.

 

    End Sub

 

#End Region

 

  End Class

 

End Namespace

Form1.Designer.vb:

Imports Inventor 

Namespace vbButton

    <Global.Microsoft.VisualBasic.CompilerServices.DesignerGenerated()> _

    Partial Class Form1

 

        Inherits System.Windows.Forms.Form

        Public Sub New(app As Inventor.Application, addInCLS As String)

        MyBase.New

        InitializeComponent

        Dim uiMgr As UserInterfaceManager =app.UserInterfaceManager

        Dim myDockableWindow As DockableWindow = uiMgr.DockableWindows.Add(addInCLS, "MyWindow", "My Add-in Dock")

        myDockableWindow.AddChild(Me.Handle)

        ' Default docking state

        If Not myDockableWindow.IsCustomized Then

            myDockableWindow.DockingState = DockingStateEnum.kFloat

            myDockableWindow.Move(25, 25, myDockableWindow.Height, myDockableWindow.Width)

        End If

        Me.Visible = true

        myDockableWindow.Visible = true

    End Sub

        'Form overrides dispose to clean up the component list.

        <System.Diagnostics.DebuggerNonUserCode()> _

        Protected Overrides Sub Dispose(ByVal disposing As Boolean)

            Try

                If disposing AndAlso components IsNot Nothing Then

                    components.Dispose()

                End If

            Finally

                MyBase.Dispose(disposing)

            End Try

        End Sub

 

        'Required by the Windows Form Designer

        Private components As System.ComponentModel.IContainer

 

        'NOTE: The following procedure is required by the Windows Form Designer

        'It can be modified using the Windows Form Designer. 

        'Do not modify it using the code editor.

        <System.Diagnostics.DebuggerStepThrough()> _

        Private Sub InitializeComponent()

            Me.ElementHost1 = New System.Windows.Forms.Integration.ElementHost()

            Me.ButtonCtrl1 = New ButtonCtrl()

            Me.SuspendLayout()

            '

            'ElementHost1

            '

            Me.ElementHost1.Dock = System.Windows.Forms.DockStyle.Fill

            Me.ElementHost1.Location = New System.Drawing.Point(0, 0)

            Me.ElementHost1.Name = "ElementHost1"

            Me.ElementHost1.Size = New System.Drawing.Size(284, 262)

            Me.ElementHost1.TabIndex = 0

            Me.ElementHost1.Text = "ElementHost1"

            Me.ElementHost1.Child = Me.ButtonCtrl1

            '

            'Form1

            '

            Me.AutoScaleDimensions = New System.Drawing.SizeF(6.0!, 13.0!)

            Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font

            Me.ClientSize = New System.Drawing.Size(284, 262)

            Me.Controls.Add(Me.ElementHost1)

            Me.Name = "Form1"

            Me.Text = "Form1"

            Me.ResumeLayout(False)

 

        End Sub

        Friend WithEvents ElementHost1 As System.Windows.Forms.Integration.ElementHost

        Friend ButtonCtrl1 As ButtonCtrl

    End Class

End Namespace

 

The following picture is the running result: (The sample WPF control is a just button with formatting text and picture tooltip)

Split a part in Inventor

By Xiaodong Liang

Issue
How can I split a part using the API? Is there any difference from part context and assembly context?

Solution
Before Inventor  2010, you can call the SplitFeatures.SplitPart method to split a part. This method takes two parameters and returns the newly created SplitFeature. Input Object SplitTool that specifies the entity that will be used to define the split. The input can be a WorkPlane, WorkSurface, or 2D Path. A Path object is obtained using the CreatePath method of the SplitFeatures object. Optional input Boolean value RemovePositiveSide that indicates which portion of the split part is to be removed. The default value is True, which indicates that the positive side will be removed.

From Inventor 2010 ,  Inventor supports multiple surface bodies. SplitFeatures.SplitPart is hidden. It will split all surface bodies. A new method is provided: SplitFeatures.TrimSolid which can split the specific surface body. 

The following code demonstrate how to use the methods,  based on the attached sample model.

The first sample passes a WorkSurface as the input to create a SplitFeature: 

 Sub splitByWorkSurface() 

 

        ' assume we have had Inventor application 

        Try

 

            Dim oDoc As PartDocument =

                _InvApplication.Documents.Add(

                   DocumentTypeEnum.kPartDocumentObject,

                 _InvApplication.FileManager.GetTemplateFile(

                 DocumentTypeEnum.kPartDocumentObject))

 

            Dim oDef As PartComponentDefinition =

                oDoc.ComponentDefinition

 

            Dim oSketch As PlanarSketch =

                oDef.Sketches.Add(oDef.WorkPlanes.Item(3))

 

            Dim oTG As TransientGeometry =

                _InvApplication.TransientGeometry

 

            oSketch.SketchLines.AddAsTwoPointRectangle(

                oTG.CreatePoint2d(0, 0),

            oTG.CreatePoint2d(6, 3))

 

            Dim oProfile As Profile =

                oSketch.Profiles.AddForSolid()

 

            Dim oBaseExtrude As ExtrudeFeature =

                oDef.Features.ExtrudeFeatures.

                          AddByDistanceExtent(

                              oProfile,

                              4,                    PartFeatureExtentDirectionEnum.kPositiveExtentDirection,

                    PartFeatureOperationEnum.kJoinOperation)

 

            oSketch =

                oDef.Sketches.Add(oDef.WorkPlanes.Item(3))

            Dim oLine As SketchLine =

                oSketch.SketchLines.AddByTwoPoints

                       (oTG.CreatePoint2d(2, -1),

                        oTG.CreatePoint2d(3, 2))

            oLine =

                oSketch.SketchLines.AddByTwoPoints

                  (oLine.EndSketchPoint,

                                               

            oTG.CreatePoint2d(2, 4))

            oProfile =

                oSketch.Profiles.AddForSurface()

 

            Dim oCutExtrude As ExtrudeFeature =              

                  oDef.Features.ExtrudeFeatures.

                       AddByDistanceExtent(

                                       oProfile,

                                       5,            PartFeatureExtentDirectionEnum.kPositiveExtentDirection,

PartFeatureOperationEnum.kSurfaceOperation)

 

            Dim oWorkSurface As WorkSurface =

                   oCutExtrude.SurfaceBody.Parent

 

            Dim oSplit As SplitFeature

 

            'before Inventor 2010

            'Set oSplit = oDef.Features.SplitFeatures.SplitPart(oWorkSurface)

 

            'From Inventor 2010

 

            ' e.g. split the first body

            oDef.Features.SplitFeatures.TrimSolid(

                oWorkSurface,

                oDef.SurfaceBodies(1),

                False)

 

        Catch ex As Exception

            MsgBox(ex.ToString())

        End Try

     End Sub

 

 

This second example passes in a 2D Path as the input to create a SplitFeature. Before running this sample, please confirm that the sketch with some SketchSpline exists and there is the part that can be split. You can use the attached part document "partTobeSplit.ipt" for the test.

 

Sub splitByPath()

  

    Try

        Dim oPart As PartDocument =

        _InvApplication.ActiveDocument

 

        Dim oDocDef = oPart.ComponentDefinition

 

    ' assume there is a sketch named 'sketch2'

    Dim oSketch As Sketch =

        oDocDef.Sketches.Item("sketch2")

 

     ' find a spline in the sketch

    Dim oSkSpLine As SketchSpline

    If oSketch.Consumed = False Then

        Dim findit As Boolean

        findit = False       

        For Each oSkSpLine In oSketch.SketchSplines

            If oSkSpLine.Construction = False Then

                findit = True

                Exit For

            End If

        Next

 

        If findit Then

            Dim oPath As Inventor.Path

            oPath =

                oDocDef.Features.

                        CreatePath(oSkSpLine)

 

            'before Inventor 2010

            'oPart.ComponentDefinition.

            'Features.SplitFeatures.SplitPart oPath, False

 

            'From Inventor 2010

            'just split second surface body

            oDocDef.Features.SplitFeatures.

                    TrimSolid(oPath,

                              oDocDef.SurfaceBodies(2),

                              False)

        End If

    End If

 

    Catch ex As Exception

        MsgBox(ex.ToString())

    End Try

 

End Sub

 

In the assembly context there is not much difference, you just need to pass in the NativeObject of the proxy object in the assembly environment to the CreatePath method when retrieving the SpitTool object. Here is an example that demonstrates how to split a part after the user selects a SketchSpline in the assembly document. Moreover, you can change the side of an existing split feature by deleting and re-creating the SplitFeature and passing in the new side parameter as shown by the last several lines.

 

 

Private Function getPath(invApp As Inventor.Application,

                         ByVal oPrtDoc As PartDocument ) _

            As Inventor.Path

 

    Dim oSks As SketchSplineProxy

 

    'We assume the user selected the sketch spline

   ' in the assembly context

    oSks =

        invApp.ActiveDocument.SelectSet(1)

 

    Dim oPrtFeats As PartFeatures =

        oPrtDoc.ComponentDefinition.Features

 

    getPath =

        oPrtFeats.SplitFeatures.CreatePath(oSks.NativeObject)

End Function

 

private Sub SplitPartInAssembly()

  

 ' assume we have had Inventor application

    Try

        Dim oAss As AssemblyDocument =

            _InvApplication.ActiveDocument

 

        'Get the first component to be split

        Dim oSelectedOcc As ComponentOccurrence =

            oAss.ComponentDefinition.Occurrences(1)

 

        Dim oPrtDoc As PartDocument =

            oSelectedOcc.Definition.Document

 

        'Get the 2D path SplitTool

        Dim oSelectedTool As Inventor.Path =

            getPath(_InvApplication,oPrtDoc)

 

        Dim oPrtFeats As PartFeatures =

            oPrtDoc.ComponentDefinition.Features

 

        ''**************before Inventor 2010***********

 

        'Create Split Part with negative side

        'Dim spFeature As SplitFeature =

   'oPrtFeats.SplitFeatures.SplitPart(oSelectedTool, False)

 

        ''Change the negative side to positive side

        'Dim skObj As Object = spFeature.SplitTool

        'spFeature.Delete(True, True, True)

 

        'spFeature =

   'oPrtFeats.SplitFeatures.SplitPart(oSelectedTool, True)

        '**************

 

        '********from Inventor 2010**********

        'Create Split Part with negative side

        Dim spFeature As SplitFeature =

            oPrtFeats.SplitFeatures.TrimSolid(

                oSelectedTool,

                oSelectedOcc.Definition.SurfaceBodies(1),

                False)

 

        'Change the negative side to positive side

        Dim skObj As Object =

            spFeature.SplitTool

        spFeature.Delete(True, True, True)

 

        spFeature = oPrtFeats.SplitFeatures.TrimSolid(

            oSelectedTool,

            oSelectedOcc.Definition.SurfaceBodies(1),

            True)

        '************************************

    Catch ex As Exception

        MsgBox(ex.ToString())

    End Try

 

End Sub

 

Download Test-part-split

Obtain 3D points along an edge

By Xiaodong Liang

Issue

I would like to obtain a listing of 3D points along a selected edge of this geometry.  Is there any functionality that would allow me to get Points from an edge at a controlled interval (e.g. return X,Y coords based on Z or return X,Y,Z based on an interval)?

Solution

The following code illustrates. Just select an Edge in your model, and the coordinates of points are output at fixed intervals along the curve (the number of intervals is determined by max_steps, which you can set in the code).

Sub GetPointsOnEdge() 

  ' assumes you have had Inventor application  

    Dim oDoc As PartDocument

    oDoc = _InvApplication.ActiveDocument

    Dim oCD As PartComponentDefinition

    oCD = oDoc.ComponentDefinition

    Dim oEdge As Edge

    oEdge = oDoc.SelectSet(1)

    Dim oCurveEvaluator As CurveEvaluator

    oCurveEvaluator = oEdge.Evaluator

    Dim length As Double

    Call oCurveEvaluator.GetLengthAtParam(0, 1, length)

    Debug.Print(length)

    Dim max_steps As Long

    max_steps = 100

    Dim par_array(max_steps) As Double

 

    Dim I As Long

    For I = 0 To max_steps

        Dim pos As Double

        pos = I * length / max_steps

        Dim par_out As Double

        Call oCurveEvaluator.GetParamAtLength(0,

                                   pos, par_out)

        par_array(I) = par_out

    Next I

 

    ' each param refers to one point with X.Y,Z values

    Dim point_array(max_steps * 3) As Double

 

    Call oCurveEvaluator.GetPointAtParam(par_array,

                                        point_array)

    ' output the points 

    For I = 0 To max_steps

        Debug.Print("Par = " & par_array(I) &

                    " Pos = (" & point_array(I * 3) & "," &

                        point_array(I * 3 + 1) & "," &

                        point_array(I * 3 + 2) & ")")

    Next I

End Sub

Quitting Inventor when Quit() doesn't

By Augusto Goncalves

Application.Quit() should normally terminate Inventor. If it does not happen, try kill the process using .NET System.Diagnostics.Process.GetCurrentProcess().Kill()

From MSDN: Note that the Kill method executes asynchronously. After calling the Kill method, call the WaitForExit method to wait for the process to exit, or check the HasExited property to determine if the process has exited.

Visit MSDN Process.Kill site for more information.

Using Attribute Sets in C#

By Augusto Goncalves

This sample code adds an Attribute Set containing a single Attribute to the first Edge in the Part Document. If the Edge already has the given Attribute, then it replaces with a new value.

Since the value type of an Attribute cannot be changed, if the Edge contains a different Attribute type with the same name, then first delete it and then add an Attribute with the new value.

The code below illustrates how to use Attributes from C#. It expects an open Part Document containing at least one Edge.

// attribute names

const string attributeSetName = "MyAttributeSet";

const string attributeName = "MyAttribute";

 

Inventor.Application app = System.Runtime.InteropServices.Marshal.

  GetActiveObject("Inventor.Application") as Inventor.Application;

Inventor.PartDocument doc =

  app.ActiveDocument as Inventor.PartDocument;

 

// Create a collection of objects

object obj = null;

Inventor.ObjectCollection objectCollection =

  app.TransientObjects.CreateObjectCollection(obj);

 

// Get one surface body edge

objectCollection.Add(

  doc.ComponentDefinition.SurfaceBodies[1].Edges[1]);

// ... you can keep on adding the objects you need to ...

 

// if OpenAttributeSets function does not find the given attribute

// set for an object in the collection, it creates one for it

Inventor.AttributeSetsEnumerator attributeSets =

  doc.AttributeManager.OpenAttributeSets(

  objectCollection, attributeSetName);

 

// you can keep changing this to check if

// assigning the new value works fine

byte[] newData = new byte[] { 5, 8, 10 };

 

// attributeSets contains the attributeSet of

// each object you added to the objectCollection

// in this case only one, the first Edge

foreach (Inventor.AttributeSet attributeSet in attributeSets)

{

  try

  {

    // if it throws exception, then it did not find the attribute

    Inventor.Attribute attribute = attributeSet[attributeName];

    // we have to initialize the array before it can be used

    byte[] oldData = attribute.Value as byte[];

 

    // if oldData is null, then it found the attribute

    // but it contains a different data type

    if (oldData == null)

    {

      // we'd better delete the old value with different

      // data type if you want ValueType to be consistent

      // with the object it stores, since we cannot change

      // the attribute.ValueType(read-only)

      attribute.Delete();

      // and then create it again with the new

      // value type - by throwing exception

      // (same as if the attribute wasn't there in the first place)

      throw new System.Exception(

        "The data type is different, " +

        " and therefore the attribute has been deleted");

    }

 

    attribute.Value = newData;

  }

  catch

  {

    // add the attribute with the new value

    attributeSet.Add(attributeName,

      Inventor.ValueTypeEnum.kByteArrayType, newData);

  }

}