This is the cadence virtuoso tool that is having the issue with geHiDragFig function.

If you're asking if there's a way to prevent nesting of commands when within geHiDragFig, then I don't believe that's possible. If you turn off "Repeat Commands" then the geHiDragFig does return, but unfortunately it returns the second point as being (say) the upper right of the rectangle drawn if you use the Create Rect command. 

So I agree, it's a bit odd - it doesn't really continue with the original behaviour once the nested command is completed.

Probably best to contact customer support. I think this will need filing a CCR with R&D.

Regards,

Andrew.

Thank you for the quick response.  That is what I am after.  In particular, when I invoke the procedure that uses this command again while it is in the command, it causes nesting of the command and somehow things get a bit weird.  Even with repeat commands off, nesting geHiDragFig, from multiple calls, still occurs and causes quirky behavior.  I am trying to prevent the user from nesting the command.  I have done so by disabling the bindkey that calls the procedure that uses the command prior to invoking the command.  Not a good approach, but works for now.

Do I file a CCR or is that something that is done by you or?

Thank you!

Adam

You need to contact customer support (I gave a link in my response above). This is for two reasons:

1. I answer questions on these forums in my spare (sort of) time. I don't have the bandwidth to handle full support cases for every issue that is beyond the scope of a quick answer here.
2. Even if I did, I don't know who you are - we really need support cases tied to the real customer rather than an anonymous handle on the forums. They get better prioritisation that way...

Then the application engineer who deals with  your case can reproduce the problem, and then report it to R&D - and it's tracked as an issue against your organisation.

Regards,

Andrew.

There are a couple things you can do to minimize your issues, although maybe not eliminate them. First, your own code can avoid nesting by checking the hiGetCurrentCmd or using hiIsFormDisplayed if your command uses a form and then exit before even calling geHiDragFig. Also, if you are using bindkeys, make sure that Enter Function bindkey option (EF) doesn't allow you to re-invoke the command. Let's say when your press "x" your command is run, then the "x EF" bindkey could just be a println statement.

Derek

Thank you, Derek.  I found the commands you gave have worked well in reducing much of the quirkiness I was experiencing with the unintentional nesting of the geHiDragFig function. 

Adam