Manufacturing DevBlog

Autodesk Inventor API Wishlist Survey, 2013

By Adam Nagy

The Wishlist Survey has closed.

Thank you to everyone who provided feedback!

Create LeaderNote.FormattedText with Document Model properties

By Augusto Goncalves

I would like to set the FormattedText of the LeaderNote to something like:

"<Property Document='model' PropertySet='Design Tracking Properties' Property='Part Number' FormatID='{32853F0F-3444-11D1-9E93-0060B03C1CA6}' PropertyID='5'>PART NUMBER</Property>"

Is there a way to do this? Yes, the code below show a sample.

Sub CreateLN()

  If m_inventorApplication.Documents.Count = 0 Then Exit Sub

 

  If m_inventorApplication.ActiveDocument.DocumentType _

    <> DocumentTypeEnum.kDrawingDocumentObject Then Exit Sub

 

  Dim oDoc As DrawingDocument

  oDoc = m_inventorApplication.ActiveDocument

  Dim s As String

  s = "<Property Document='model' " _

    & "PropertySet='Design Tracking Properties' " _

    & "Property='Part Number' " _

    & "FormatID='{32853F0F-3444-11D1-9E93-0060B03C1CA6}' " _

    & "PropertyID='5'>PART NUMBER</Property>"

 

  ' Create a DrawingView on this Sheet and 

  ' the first DrawingCurve is line curve.

  Dim oGI As GeometryIntent

  oGI = oDoc.ActiveSheet.CreateGeometryIntent( _

    oDoc.ActiveSheet.DrawingViews(1). _

    DrawingCurves.Item(1), _

    PointIntentEnum.kStartPointIntent)

  Dim oObjCol As ObjectCollection

  oObjCol = m_inventorApplication.TransientObjects. _

    CreateObjectCollection

  oObjCol.Add(oGI)

 

  Dim oLN As LeaderNote

  oLN = oDoc.ActiveSheet.DrawingNotes. _

    LeaderNotes.Add(oObjCol, s)

End Sub

Use | “OR” with DefaultAcquisitionOption to Download & CheckOut with AcquireFiles

By Wayne Brill

The Vault 2014 API documentation does not explicitly describe how to  download and checkout a file using AcquireFiles. To do this you can "OR" together the AcquisitionOption enumeration Checkout and Download .

Here is an update to the downloadFile function in the VaultBrowser SDK sample that does a checkout and download.

 

private static void downloadFile

    (VDF.Vault.Currency.Connections.Connection

                                   connection,

    VDF.Vault.Currency.Entities.FileIteration

                                        file,

                           string folderPath)

{

    VDF.Vault.Settings.AcquireFilesSettings

        settings = new VDF.Vault.Settings.

           AcquireFilesSettings(connection);

 

    settings.AddEntityToAcquire(file);

 

    settings.DefaultAcquisitionOption =

     VDF.Vault.Settings.AcquireFilesSettings.

              AcquisitionOption.Checkout |

     VDF.Vault.Settings.AcquireFilesSettings.

                 AcquisitionOption.Download;

 

        settings.LocalPath =  new VDF.Currency.

        FolderPathAbsolute(folderPath);

 

    connection.FileManager.AcquireFiles(settings);

}

Create PDF C++ Example

By Wayne Brill

There is a VBA example that uses the PDF translator in the Inventor API help file. Here is an example in C++. You can  replace the code in the SimpleExe SDK example to test this code.  (At this location on my system)  

"C:\Users\Public\Documents\Autodesk\Inventor 2014\SDK\DeveloperTools\Samples\VC++\Standalone Applications\Inventor\SimpleExe"

It creates a pdf for each sheet and one PDF with all the sheets.

<code_begin>
// SimpleExe.cpp : Defines the entry point for the console application.

#include "stdafx.h"

// Forward declarations
static HRESULT PrintPDF();

// Main. Note that all COM related activity (including the automatic 'release' within smart
// pointers) MUST take place BEFORE CoUnitialize(). Hence the function 'block' within which
// the smart-pointers construct and destruct (and AddRef and Release) keeping the CoUnitialize
// safely out of the way.

int _tmain(int argc, _TCHAR* argv[])
{
HRESULT Result = NOERROR;

Result = CoInitialize (NULL);

if (SUCCEEDED(Result))
Result = PrintPDF();

CoUninitialize();

return 0;
}

static HRESULT PrintPDF()
{
HRESULT Result = NOERROR;

CLSID InvAppClsid;
Result = CLSIDFromProgID (L"Inventor.Application", &InvAppClsid);
if (FAILED(Result)) return Result;

CComPtr<IUnknown> pInvAppUnk;
Result = ::GetActiveObject (InvAppClsid, NULL, &pInvAppUnk);
if (FAILED (Result))
{
_tprintf_s (_T("*** Could not get hold of an active Inventor application ***\n"));
return Result;
}

CComPtr<Application> pInvApp;
Result = pInvAppUnk->QueryInterface (__uuidof(Application), (void **) &pInvApp);
if (FAILED(Result)) return Result;

CComPtr<Document> pDoc;
Result = pInvApp->get_ActiveDocument(&pDoc);
if (FAILED(Result)) return Result;

CComQIPtr<DrawingDocument> pDrawDoc = pDoc;

// Get the PDF translator Add-In.
CComPtr<ApplicationAddIns> pAddIns;
Result = pInvApp->get_ApplicationAddIns(&pAddIns);

CComPtr<ApplicationAddIn> pAddIn;
Result = pAddIns->get_ItemById(_bstr_t("{0AC6FD96-2F4D-42CE-8BE0-8AEA580399E4}"), &pAddIn);
 
CComQIPtr<TranslatorAddIn> pTransAddIn = pAddIn;

CComPtr<TransientObjects> pTransObjects;
Result = pInvApp->get_TransientObjects(&pTransObjects);

// Create the context.
CComPtr<TranslationContext> pContext;
Result = pTransObjects->CreateTranslationContext(&pContext);
Result = pContext->put_Type(kFileBrowseIOMechanism);

// Create a NameValueMap object
CComPtr<NameValueMap> pOptions;
Result = pTransObjects->CreateNameValueMap(&pOptions);

// Create a DataMedium object
CComPtr<DataMedium> pDataMedium;
Result = pTransObjects->CreateDataMedium(&pDataMedium);

// Check whether the translator has 'SaveCopyAs' options
VARIANT_BOOL hasOptions;
Result = pTransAddIn->get_HasSaveCopyAsOptions(pDrawDoc, pContext, pOptions, &hasOptions);
if (Result == S_OK)
{
CComPtr<Sheets>pSheets;
Result = pDrawDoc->get_Sheets(&pSheets);

long sheetCount;
Result = pSheets->get_Count(&sheetCount);

if (true)
{
for( int i=1; i<=sheetCount; ++i)
{
Result = pOptions->put_Value(_bstr_t("Vector_Resolution"), CComVariant(400));

Result = pOptions->put_Value(_bstr_t("Sheet_Range"), CComVariant(kPrintSheetRange));
Result = pOptions->put_Value(_bstr_t("Custom_Begin_Sheet"), CComVariant(i));
Result = pOptions->put_Value(_bstr_t("Custom_End_Sheet"), CComVariant(i));

//Set the destination file name
char filename[100];
sprintf_s(filename, "c:\\temp\\test%d.pdf", i);

pDataMedium->put_FileName(_bstr_t(filename));

// Publish document.
Result = pTransAddIn->SaveCopyAs(pDrawDoc, pContext, pOptions, pDataMedium);

}
  
Result = pOptions->put_Value(_bstr_t("Sheet_Range"), CComVariant(kPrintAllSheets));
Result = pOptions->put_Value(_bstr_t("Custom_Begin_Sheet"), CComVariant(1));
Result = pOptions->put_Value(_bstr_t("Custom_End_Sheet"), CComVariant(sheetCount));
pDataMedium->put_FileName(_bstr_t("c:\\temp\\testPDF_all_Sheets_in_one.pdf"));

// Publish document.
Result = pTransAddIn->SaveCopyAs(pDrawDoc, pContext, pOptions, pDataMedium);
}
else
{
Result = pOptions->put_Value(_bstr_t("Vector_Resolution"), CComVariant(400));
Result = pOptions->put_Value(_bstr_t("Sheet_Range"), CComVariant(kPrintSheetRange));
Result = pOptions->put_Value(_bstr_t("Custom_Begin_Sheet"), CComVariant(1));
Result = pOptions->put_Value(_bstr_t("Custom_End_Sheet"), CComVariant(sheetCount));
 
//Set the destination file name
char filename[500];
sprintf_s(filename, "c:\\temp\\testAll.pdf");

pDataMedium->put_FileName(_bstr_t(filename));

// Publish document.
Result = pTransAddIn->SaveCopyAs(pDrawDoc, pContext, pOptions, pDataMedium);
}
}

return Result;
}

<code_end>

Create simplified part by API

by Xiaodong Liang

The [Create Simplified Part] actually creates a derived assembly for the new part document. You will firstly create DerivedAssemblyDefinition, and configure the relevant options, finally add it to the new part by DerivedAssemblyComponents.Add.

 

The following is a small code demo. 

Sub CreateSimplifiedPart()

' Set a reference to the active assembly document
Dim oDoc As AssemblyDocument
Set oDoc = ThisApplication.ActiveDocument

Dim oDef As AssemblyComponentDefinition
Set oDef = oDoc.ComponentDefinition

' Create a new part document that will derive the assembly
Dim oPartDoc As PartDocument
Set oPartDoc = ThisApplication.Documents.Add(kPartDocumentObject, , True)

Dim oPartDef As PartComponentDefinition
Set oPartDef = oPartDoc.ComponentDefinition

Dim oDerivedAssemblyDef As DerivedAssemblyDefinition
Set oDerivedAssemblyDef = oPartDef.ReferenceComponents.DerivedAssemblyComponents.CreateDefinition(oDoc.FullDocumentName)

' Set various related options
oDerivedAssemblyDef.DeriveStyle = kDeriveAsSingleBodyNoSeams
oDerivedAssemblyDef.IncludeAllTopLevelWorkFeatures = kDerivedIncludeAll
oDerivedAssemblyDef.IncludeAllTopLevelSketches = kDerivedIncludeAll
oDerivedAssemblyDef.IncludeAllTopLeveliMateDefinitions = kDerivedExcludeAll
oDerivedAssemblyDef.IncludeAllTopLevelParameters = kDerivedExcludeAll
oDerivedAssemblyDef.ReducedMemoryMode = True
Call oDerivedAssemblyDef.SetHolePatchingOptions(kDerivedPatchAll)
Call oDerivedAssemblyDef.SetRemoveByVisibilityOptions(kDerivedRemovePartsAndFaces, 25)

' Create the shrinkwrap component
Dim oDerivedAssembly As DerivedAssemblyComponent
Set oDerivedAssembly = oPartDef.ReferenceComponents.DerivedAssemblyComponents.Add(oDerivedAssemblyDef)

 'save the new part file
Call oPartDoc.SaveAs("c:\temp\newpart.ipt", False)
  
End Sub

 

 

Why can I not convert linear Edges to Lines?

By Augusto Goncalves

Why can I not convert linear Edges to Lines? Perhaps the name is a bit misleading, but Line in Inventor API represents a straight line with infinite length. It only has a 'RootPoint' and a 'Direction'. In most scenarios, the LineSegment object can do the trick.

Dim oDoc As PartDocument

oDoc = m_inventorApplication.ActiveDocument

Dim oEdge As Edge

oEdge = oDoc.ComponentDefinition.SurfaceBodies(1).Faces(1).Edges(1)

Dim oLineSeg As LineSegment

If TypeOf oEdge.Geometry Is LineSegment Then

  oLineSeg = oEdge.Geometry

End If

Insert Content Center Part

By Adam Nagy

You can insert Content Center parts programmatically. The following sample is looking through the whole Content Center content in order to find a specific part based on its display name.

Public Function GetFamily( _
name As String, node As ContentTreeViewNode) _
As ContentFamily
  Dim cc As ContentCenter
  Set cc = ThisApplication.ContentCenter
    
  If node Is Nothing Then Set node = cc.TreeViewTopNode
  
  Dim cf As ContentFamily
  For Each cf In node.Families
    If cf.DisplayName = name Then
      Set GetFamily = cf
      Exit Function
    End If
  Next
  
  Dim child As ContentTreeViewNode
  For Each child In node.ChildNodes
    Set cf = GetFamily(name, child)
    If Not cf Is Nothing Then
      Set GetFamily = cf
      Exit Function
    End If
  Next
End Function

Public Sub CcTest()
   Dim asm As AssemblyDocument
   Set asm = ThisApplication.ActiveDocument
   
   Dim cf As ContentFamily
   Set cf = GetFamily("CCPart", Nothing)
   
   Dim member As String
   Dim ee As MemberManagerErrorsEnum
   member = cf.CreateMember(1, ee, "Problem")
   
   Dim tg As TransientGeometry
   Set tg = ThisApplication.TransientGeometry
   
   Call asm.ComponentDefinition.Occurrences.Add( _
    member, tg.CreateMatrix())
End Sub

Get WebServiceManager in a Vault Event handler

By Wayne Brill

It is not obvious how to get the WebServiceManager in a WebService extension event handler. One of the arguments passed into the event is named “sender” by default. (A Vault event handler will have a sender and event arguments). The sender argument is simple object but it can be cast it to IWebService. You can use IWebService to create WebServiceCredentials and this can be used to create new instance of WebServiceManager. Here is a C# example of an event handler that gets the WebServiceManager:

 

void UpdateItemLifecycleStateEvents_Pre_wb

     (object sender,

       UpdateItemLifeCycleStateCommandEventArgs e)

{

    Autodesk.Connectivity.WebServicesTools.

        WebServiceCredentials CurrentCredentials =

                        new Autodesk.Connectivity.

           WebServicesTools.WebServiceCredentials

                            ((IWebService)sender);

 

    Autodesk.Connectivity.WebServicesTools.

        WebServiceManager ServiceManager =

                   new Autodesk.Connectivity.

          WebServicesTools.WebServiceManager

                             (CurrentCredentials);

 

    MessageBox.Show("From Event");

}

 

Note: Some operations may not work correctly when it’s executed from event handler (i.e. modifying of mapped properties when file is already open in Inventor). For such cases the safer approach may be to schedule a job and perform operation later.

find components displaying in section drawing view

By Xiaodong Liang

I noticed one forum post my colleague Philippe has helped. I think it may help some customers. This question is to traverse the components which display in the section drawing view.

There is not a direct way, but possible with API.

You could either iterate through all occurrences of your top level assembly and see if "DrawingView.DrawingCurves(occurrence)" returns something, if yes the component is part of the view.

Or the other way around, iterate through all the DrawingCurves in the specific view and check "DrawingCurve.ModelGeometry" to see which occurrence this belong to.

The code below is a small demo. It assumes the second view of the sheet is a section view.

Public Sub GetViewComponents()

    Dim doc As DrawingDocument
    Set doc = ThisApplication.ActiveDocument
    
    Dim sectionView As SectionDrawingView
    Set sectionView = doc.ActiveSheet.DrawingViews(2)
    
    Dim docDesc As DocumentDescriptor
    Set docDesc = sectionView.ReferencedDocumentDescriptor

    Dim asm As AssemblyDocument
    Set asm = docDesc.ReferencedDocument
    
    Debug.Print "Occurrences in View: " & sectionView.name
    
    On Error Resume Next
    
    Dim occurrence As ComponentOccurrence
    For Each occurrence In asm.ComponentDefinition.Occurrences
    
        Dim curves As DrawingCurvesEnumerator
        Set curves = sectionView.DrawingCurves(occurrence)
        
        If Err Then
            'DrawingCurves fails if no curves...
            Err.Clear
        ElseIf curves Is Nothing Or curves.count = 0 Then
            'Component not in view...
        Else
            'Component is in section view
            Debug.Print occurrence.name
        End If
    
    Next
    
End Sub

Deadlock using AcquireFiles() Vault 2014

By Wayne Brill

There is a known issue where the AcquireFiles() function can stop responding. (This will be addressed in a future service pack). 

Here is some detail about this issue: The Vault Development Framework (VDF) needs to be initialized and told whether it is operating in the context of a UI application or not (if not specified, it will make the assumption that this *is* a UI application).  During download some of the “file reference update” extension handlers (e.g. Inventor, AutoCAD specific code) will do their work on the main UI thread (if the application is indeed a UI based application).  If the VDF thinks it is operating in the context of a UI application but it is not, (2014 JobProcessor) then you *may* (not always—it depends on whether or not file references need to be updated, and what type of file you are downloading) end up with a deadlock during AcquireFiles.

In 2013, the JobProcessor was one UI application (and thus initializing the VDF as a UI application was appropriate).  In 2014, the JobProcessor has a UI component (JobProcessor.exe) and a non-UI component (Connectivity.JobProcessor.Delegate.Host.exe).  The Connectivity.JobProcessor.Delegate.Host.exe is where the job handlers run. 

Solution:

As early as possible in your Job Handler’s implementation of IJobHandler.Execute, add the following line:
Autodesk.DataManagement.Client.Framework.Library.Initialize(false /* ui Application */);

Note: Console applications should add this line also (Under the right circumstances, it can encounter this same deadlock).

Webinar announcement

By Stephen Preston

Register and mark your calendars now for this upcoming webcast on making the most of the Autodesk Exchange Apps store ...

"How developers can ride and profit from the adoption wave of Autodesk Exchange Apps"

The Autodesk Exchange Apps stores (currently there are 15 stores) are a huge opportunity for developers to gain direct access to the growing number of Autodesk customers using Exchange Apps.  In just one year there’s been over one million visits and over 250,000 downloads. With comments like “one of my most useful tools”, “love this app, saved me hours of work” there’s no doubt that Exchange Apps has become a resource that Autodesk customers rely on to find useful apps of all types.    

If you develop apps and want to reach more customers quickly, easily and inexpensively but haven’t yet put your toe in the water with Exchange Apps, the Autodesk Developer Network (ADN) team is ready to help you.  You’re invited to attend a webinar on June 13^th hosted by Jim Quanci and Stephen Preston to learn how you can catch the wave and accelerating growth of Exchange Apps.

You’ll learn the tricks of the trade when publishing on Exchange Apps, get ideas on how to be successful and learn about the ability to publish localized apps. Here’s what you need to know:

Webinar details:

Date: Thursday, June 13^th, 2013
Time: 8 a.m. PDT (4 p.m. BST; 5 p.m. CET; 11 a.m. EDT)
Duration: Approximately one hour

Open to anyone interested in publishing apps on Autodesk Exchange Apps (i.e. ADN membership is not required :-).

Registration: Reserve your place by June 11 by sending an email to adn-training-worldwide@autodesk.com with Exchange Apps webinar as the subject. Please make sure you include your full name, company name and email address.

And visit www.autodesk.com/developapps now if you want a head start in learning how to publish apps.