Control is not coming out from leHiCreatePath() fn due to ne

[Pratheesh.s]

Hi,

We are developing a checklist automation tool for Virtuoso LE. We need
to prevent user from things like "long routing of poly". I could not
find any trigger functions in skill to call our functions at the time
of leHiCreatePath(). So I have assigned a bind key which calls our fn
and runs leHiCreatePath(). But the issue is leHiCreatePath()
is recursivly calling itself.So control is not moving down

hiSetBindKey("Layout" "<key>p" "polyLenCheckWp()")
procedure(polyLenCheckWp()
lenCountWv=0
leHiCreatePath()
lengthFn()
displayFn()
)

Control is stucked at leHiCreatePath() and not going to lengthFn() &
displayFn().until the user presses escape.(but I cant wait till esc)

Can you please help me...

Regards,

Pratheesh S
AMS-Wipro Technologies

 

[Riad KACED]

Hi,

I don't see how to workaround this interactive function off the top of
my head.
I would rather advice using the enterPath fucntion along with the
dbCreatePath function. This way, you could control what you are
drawing based on the points, width ... etc of your path.
That's the best solution I could see so far ... Other chaps might have
better ideas !

Cheers,
Riad.

 

[Andrew Beckett]

Pratheesh.s wrote, on 11/14/08 13:42:

Hi,

We are developing a checklist automation tool for Virtuoso LE. We need
to prevent user from things like "long routing of poly". I could not
find any trigger functions in skill to call our functions at the time
of leHiCreatePath(). So I have assigned a bind key which calls our fn
and runs leHiCreatePath(). But the issue is leHiCreatePath()
is recursivly calling itself.So control is not moving down

hiSetBindKey("Layout" "<key>p" "polyLenCheckWp()")
procedure(polyLenCheckWp()
lenCountWv=0
leHiCreatePath()
lengthFn()
displayFn()
)

Control is stucked at leHiCreatePath() and not going to lengthFn() &
displayFn().until the user presses escape.(but I cant wait till esc)

Can you please help me...

Regards,

Pratheesh S
AMS-Wipro Technologies

The only way would be to turn off the "Repeat Commands" option in the
Options->Editor Options form. Otherwise it keeps in the same function until you
hit escape.

However, I would suggest that the approach of having to look over the entire
design for long paths is going to be problematic (i.e. slow) when you have a
large design - if you're doing this after every single edit operation.

Perhaps it should be an elective check - i.e. something that has to be run like DRC.

Andrew.