:IviMateConstraint with two mates with same name

[scottheide]

:IviMateConstraint seems to be working well for us with one exception.  In some cases we have a part with two iMates with the same name.   The interactive Inventor Place command knows to go to he unused iMate if one of them is already used.  (Also, I believe the API "AddPart" method probably does the same thing.)   However, the Intent :IviMateConstraint object doesn't seem to be so smart, it just puts both objects on the same iMate (the first one).  

Any ideas how to control this so that we can mate parts to each iMate?

Using the Inventor API we can get access to the unique mate "identifier" for each mate.  I'm not sure what to do with it though.

Any ideas or help would be greatly appreciated.

Thanks!

Scott

[wayne.brill]

Hi Scott,

Can you provide a small dataset that will allow me to recreate this behvior? I will research it and report the behavior to engineering if there is no solution. (If you have solved the problem please let me know).

Thanks,

Wayne