Steve, The problem it turns out is not LAST. Both your and Matt's examples worked helped answer my original question and I can get the explicit index precisely. The problem is that the explicit index for LAST physically changes if some other component is removed from the topology.
It's something I can circumvent but will require something with a bit more sophistication to track the index changes manually. Luckily its predictable. If you know what edge you are deleting for example, that's the index the LAST edge changes to, then LAST moves down line. Oh fun. -- Joey Ponthieux LaRC Information Technology Enhanced Services (LITES) Mymic Technical Services NASA Langley Research Center __________________________________________________ Opinions stated here-in are strictly those of the author and do not represent the opinions of NASA or any other party. From: [email protected] [mailto:[email protected]] On Behalf Of Steven Caron Sent: Wednesday, April 03, 2013 2:22 PM To: [email protected] Subject: Re: LAST component ya, don't save 'edge[LAST]' get your selection as a subcomponent and get the index, both that link and matt's example code should get you up to speed with this part of the API On Wed, Apr 3, 2013 at 11:12 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] <[email protected]<mailto:[email protected]>> wrote: Hmmm. I think the problem I have is more complicated than I realized. edge[LAST] is in my saved pre-selection If I delete an arbitrary edge, say edge[64] edge[LAST], or 120, then becomes edge[64] edge["whatever"], probably 119, becomes edge [LAST] assuming I add more edges, reselecting the saved selection then selects an edge other than 64, when 64 is what I really want because it was originally 120.
