Access 3D-Sketches in Assembly with API
Accepted solution
Since you can access the API by several different means, I thought I would show the regular iLogic way to do it.
Here is a simple iLogic rule you can use to toggle the visibility of all 3D sketches in all parts within the active assembly.
If ThisApplication.ActiveDocumentType <> DocumentTypeEnum.kAssemblyDocumentObject Then
MsgBox("This rule '" & iLogicVb.RuleName & "' only works for Assembly Documents.",vbOKOnly, "WRONG DOCUMENT TYPE")
Return
End If
Dim oADoc As AssemblyDocument = ThisAssembly.Document
Dim oOnOff As Boolean
For Each oRefDoc As Document In oADoc.AllReferencedDocuments
If oRefDoc.DocumentType = DocumentTypeEnum.kPartDocumentObject Then
Dim oPDoc As PartDocument = oRefDoc
If oPDoc.ComponentDefinition.Sketches3D.Count > 0 Then
For Each oSketch3D As Sketch3D In oPDoc.ComponentDefinition.Sketches3D
oOnOff = oSketch3D.Visible
oSketch3D.Visible = (Not oOnOff)
Next
End If
End If
NextIf you want to change this rule from a toggle functionality to a direct (turn them all off) functionality, all you need to do is
- assign the value of False to the Boolean variable near the beginning of the code (it should already be false though, by default)
- Replace these two lines [oOnOff = oSketch3D.Visible] & [oSketch3D.Visible = (Not oOnOff)] with the following:
- oSketches3D.Visible = oOnOff
Like this:
If ThisApplication.ActiveDocumentType <> DocumentTypeEnum.kAssemblyDocumentObject Then
MsgBox("This rule only works for Assembly Documents.",vbOKOnly, "WRONG DOCUMENT TYPE")
Return ' or Exit Sub
End If
Dim oADoc As AssemblyDocument = ThisAssembly.Document
Dim oOnOff As Boolean = False
For Each oRefDoc As Document In oADoc.AllReferencedDocuments
If oRefDoc.DocumentType = DocumentTypeEnum.kPartDocumentObject Then
Dim oPDoc As PartDocument = oRefDoc
If oPDoc.ComponentDefinition.Sketches3D.Count > 0 Then
For Each oSketch3D As Sketch3D In oPDoc.ComponentDefinition.Sketches3D
oSketch3D.Visible = oOnOff
Next
End If
End If
NextIf this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click 'LIKE' 👍.
If you have time, please... Vote For My IDEAS 💡and Explore My CONTRIBUTIONS
Inventor 2020 Help | Inventor Forum | Inventor Customization Forum | Inventor Ideas Forum
Wesley Crihfield
(Not an Autodesk Employee)
Glad I could help. 🙂
Just in cast you weren't aware though, the codes provided by @el_jefe_de_steak were VBA code. You wouldn't be able to run these directly within an iLogic rule, like the code I posted. To use the VBA code, you would open your VBA Editor [Tools tab > Options panel > VBA Editor] then create a new Module under either your ApplicationProject or under a DocumentProject, then paste that code into that module. (If under the DocumentProject, it will only be available to that document.) Once you have done this the code in that module becomes what is known as a VBA Macro. The Macro will be named according to the name of the Module and the name of the first Public Sub or Function within that module. Then when you are outside of the VBA Editor, you can click the Macros button [Tools tab > Options panel > Macros], which will open a small dialog box. Then in the drop-down list beside "Macros in:", select the Project you placed the Module under. Then all available Modules within that Project will show in the "Macro name:" window above that. Select the one you want, then click Run.
Or, if you're already familiar with all that, then you may also know that you can create a button within you ribbon to represent a macro, and that clicking this button will run the macro. This is what he was referring to at the beginning of the second post.
You can also run iLogic rules from VBA macros, by telling the macro to run the iLogic rule (not by pasting iLogic code into the module). There are several posts here on this forum that can show you how to do this if that's what you were hoping for.
Wesley Crihfield
(Not an Autodesk Employee)