Community
Fusion API and Scripts
Got a new add-in to share? Need something specialized to be scripted? Ask questions or share what you’ve discovered with the community.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

UserInterface.selectEntity - what are the possible options?

2 REPLIES 2
Reply
Message 1 of 3
banshee10
451 Views, 2 Replies

UserInterface.selectEntity - what are the possible options?

UserInterface.selectEntity says that the filter parameter is "A string defining the types of entities valid for selection. This uses the same strings that the SelectionCommandInput uses. You can combine multiple types by using a comma delimiter. For example, the string "PlanarFaces,ConstructionPlanes" will allow the selection of either a planar face or a construction plane."

 

But I don't see anything under SelectionCommandInput that talks about the possible values.

 

(A comma-separated string seems like a strange choice of type for this parameter, too.)

----
James Moore
james@restphone.com
2 REPLIES 2
Message 2 of 3
marshaltu
in reply to: banshee10

Hello,

 

I am sorry to hear you run into the trouble. It was known issue(missing help for selection filters) and we plan to do improvement in future releases.

 

I would post those selection strings here so that you can work it around right away. We are thinking the best way how to define selection filters and make them be easy to use.

 

Thanks,

Marshal

 

-----

"Bodies"
"SolidBodies"
"SurfaceBodies"
"Faces"
"SolidFaces"
"SurfaceFaces"
"PlanarFaces"
"CylindricalFaces"
"ConicalFaces"
"SphericalFaces"
"ToroidalFaces"
"SplineFaces"
"Edges"
"LinearEdges"
"CircularEdges"
"EllipticalEdges"
"TangentEdges"
"NonTangentEdges"
"Vertices"
"RootComponents"
"Occurrences"
"Sketches"
"SketchCurves"
"SketchLines"
"SketchCircles"
"SketchPoints"
"ConstructionPoints"
"ConstructionLines"
"ConstructionPlanes"



Marshal Tu
Fusion 360 Developer
Autodesk, Inc.

Message 3 of 3
KrisKaplan
in reply to: marshaltu

But note that you should not really copy these string literals into your code.  They are defined as string constants on the SelectionCommandInput class.  For example SelectionCommandInput.PlanarFaces and SelectionCommandInput.ConstructionPlanes.  It would be preferrable to use these constants.  This should help prevent any typos in the strings (a typo in the constant name would either be highlighted as undefined by the code editor or present a better runtime error, where a typo in a string would only cause a runtime error as an invalid argument), and code editors should give you some intellisense help as well.

 

Kris



Kris Kaplan

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report