SSNAMEX documentation omission

SSNAMEX documentation omission

dbroad
Mentor Mentor
786 Views
2 Replies
Message 1 of 3

SSNAMEX documentation omission

dbroad
Mentor
Mentor

Return values from ssnamex have more information in them than the documentation indicates. For example, when a picked object is selected as part of a ssget, let's say the first object for example. If that object is a nested attribute reference, then there is information in the ssnamex return value that indicates which attribute it it. This is not documented. In the following hypthetical example, based on the documentation, the object is selected by pick (first number is 1), the parent entity is 1d62da0, and the nested entity picked is the 6th attribute following the block reference parent. The examples only show the number after the ename being 0 and never mention another use. 


((1 <Entity name: 1d62da0> 6 (0 (1.0 1.0 0.0))))

 

The 0th entity after the parent entity would mean that the parent block reference object was selected rather than an attribute. Such a return value would look like below.

((1 <Entity name: 1d62da0> 0 (0 (1.0 1.0 0.0))))

Architect, Registered NC, VA, SC, & GA.
787 Views
2 Replies
Replies (2)
Message 2 of 3

john.uhden
Mentor
Mentor

Pretty neat, Doug.  I wonder how you figured that out.

 

But the attribute picks have to be direct hits, like entsel, right?  I mean you can't use window or crossing to get them, can you?

Yes, I know that if you select a block with attributes that you can process through its children, but I was thinking about getting only the selected attributes without direct hits.

John F. Uhden

0 Likes
Message 3 of 3

dbroad
Mentor
Mentor

I just asked myself why the number was always 0 in the documentation.  I did a test by using ssnamex on an ssget after directly picking an attribute.  Then I repeated the process with different attributes.  The numbers matched which attribute was actually picked.  Other selection modes don't return that information as far as I know.

Architect, Registered NC, VA, SC, & GA.
0 Likes