iLogic to turn off ALL sketches vibibility

[Anonymous]

Hi,

I know this subject as been posted often but I can't seem to find exactly what i'm looking for.

I need some help on creating an iLogic code to put ALL sketches visibility at off in an assembly once we are done. I know that ALL is a concept too large but can I define a list of sketch names? We have establish (sort of) a naming convention for principal sketches but I'm sure users can reverse words or use capital letters or what ever... Can I say to look for skecthes containing certain words or I need to be specific for the rule to work properly?

I found useful threads but I don't know how to adapt the code for my needs.

Thanks,

[mdavis22569]

I don't know the code for it ...however You know you can go right to View, Object Visibility and click all work features and that'll do it too

[Curtis_W]

---

@Anonymous wrote:
I don't know the code for it ...however You know you can go right to View, Object Visibility and click all work features and that'll do it too

---

Hi michaeldavis7418,

Just a reminder that using the View >  Object Visibility option sets an override, but does not actually toggle the sketch visibiltiy on/off option.

 Josy05,

I'll look for some iLogic code to do this later, when I have a moment.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[Curtis_W · Accepted solution]

Hi  Josy0, 

Here is the iLogic code to turn off the visibility of all the 2D sketches in the part:

Dim doc As PartDocument
doc = ThisDoc.Document

Dim oSketch As PlanarSketch
For Each oSketch In doc.ComponentDefinition.Sketches
oSketch.Visible = False 
Next

 I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[Anonymous]

Thanks Curtis, your version of the code is simpler and works perfectly.

At first I thought of adding a message box to warn the users then I said why not give the choice. Is that possible? Can I have active button permitting the users not to close the sketch visibility is they desire? Because at the moment Yes or No does no make a difference, the sketches will turn off anyway.

[Anonymous]

I found it on my own and the answer was on your blog.

[DClunie]

Will this code work at assembly level.

Can it switch off on all parts found ??

[darrell.wcd]

is it possible to do this from an assembly level?

that way i can create a trigger that will turn the sketches in all parts off.

[johnsonshiue]

Hi! Just in case you were not aware of Object Visibility. You can go to View -> Object Visibility -> turn off all objects at the assembly level. Please note that the change only applies to the the assembly. The objects may still be visible within their documents or other documents.

Many thanks!

[aniketpunwatkar · Accepted solution]

Hello,

           I have worked on this code works super fine.

Don't need high end logic or complex code.it is as simple as poem to read

Dim doc As AssemblyDocument
 doc = ThisApplication.ActiveDocument

If Not doc Is Nothing Then

Dim asmCompDef As AssemblyComponentDefinition
asmCompDef=doc.ComponentDefinition

Dim comp As ComponentOccurrence
For Each comp In asmCompDef.Occurrences.AllLeafOccurrences
	
	
If comp.ReferencedDocumentDescriptor.ReferencedDocument.DocumentType = DocumentTypeEnum.kPartDocumentObject Then
	
		
Dim compDef As PartComponentDefinition
comDef = comp.ReferencedDocumentDescriptor.ReferencedDocument.ComponentDefinition


		
Dim sw As Inventor.Sketch
For Each sw In comDef.Sketches
	sw.Visible = Not sw.Visible
Next sw



Dim wp As WorkPoint
For Each wp In comDef.WorkPoints
	wp.Visible = Not wp.Visible
Next wp
	
Dim pl As WorkPlane
For Each pl In comDef.WorkPlanes
	pl.Visible = Not pl.Visible
Next pl

End If
	
Next comp

End If
	
	

[nathan_m_gardner]

I get this error message when I run this code. I have colored the line it errors out on.

System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at Inventor.Sketch.set_Visible(Boolean )
at ThisRule.Main() in rule: test, in document 335850.iam:line 23
at Autodesk.iLogic.Exec.AppDomExec.ExecRuleInAssembly(Assembly assem)
at iLogic.RuleEvalContainer.ExecRuleEval(String execRule)

Dim doc As AssemblyDocument
 doc = ThisApplication.ActiveDocument

If Not doc Is Nothing Then

Dim asmCompDef As AssemblyComponentDefinition
asmCompDef=doc.ComponentDefinition

Dim comp As ComponentOccurrence
For Each comp In asmCompDef.Occurrences.AllLeafOccurrences
	
	
If comp.ReferencedDocumentDescriptor.ReferencedDocument.DocumentType = DocumentTypeEnum.kPartDocumentObject Then
	
		
Dim compDef As PartComponentDefinition
comDef = comp.ReferencedDocumentDescriptor.ReferencedDocument.ComponentDefinition


		
Dim sw As Inventor.Sketch
For Each sw In comDef.Sketches
	sw.Visible = Not sw.Visible
Next sw



Dim wp As WorkPoint
For Each wp In comDef.WorkPoints
	wp.Visible = Not wp.Visible
Next wp
	
Dim pl As WorkPlane
For Each pl In comDef.WorkPlanes
	pl.Visible = Not pl.Visible
Next pl

End If
	
Next comp

End If

 I have colored  

[WCrihfield]

Hi @nathan_m_gardner.  You may have to get a reference to the Document object that the leaf occurrence is referencing, then check its Document.IsModifiable property first.  If its value is False, then skip that one, because you will not be able to make changes to it.  Then, only if its value is True, access its ComponentDefinition, then the visibility settings.  Just one possibility.  Content Center stuff, as well as any models referencing files that are located in a 'Library' location, are usually ReadOnly, but those are not the only ones.  Sometimes having multiple ModelStates in referenced model files, then including multiple ModelState versions of that model in an assembly as different components can cause them to be treated as ReadOnly, because it thinks they are 'ModelState members' instead of 'a ModelState factory'.  We can only write to one ModelState representation of a model file at a time, so when multiple versions are open at the same time, because they are being referenced by open assemblies or drawings, that can cause complex issues.