Stats

  • Locked Locked
  • Replies 5
  • Subscribers 142
  • Views 13756
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

hiRegCurWindowTrigger usage

RK56

Hi,

What is this function hiRegCurWindowTrigger? How to use this? I tried the following

procedure(testPrint(win)

printf("%L\tgot modified", win)

)

hiRegCurWindowTrigger('testPrint)

-Ramakrishnan

  • Hi Ramakrishnan,

    The documentation seems pretty clear to me. It does get passed a window number rather than a window id, so you'd have to use window(win) to get the corresponding window id. What is unclear about it? By the way, it's nothing to do with the window being "modified" - it's just whenever the current window changes (Virtuoso's idea of which window is active - the window that has the window number in the bottom left coloured in a pink-ish colour).

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Your reply cleared the confusion. I thought this function will be triggered for events like some object is selected or some object is created/modified/moved/deleted.

    Is there any function to do the above in layout/schematic/symbol?

    -Ramakrishnan

  • in reply to RK56

    There is for selection in layout - use leRegUserObjectSelectionFilter. However, the answer is "no" for the other operations in layout, and no for any of the operations in schematic or symbol.

    Andrew.

  • in reply to Andrew Beckett

    Ok. Thanks for the information. Looks like such API is not available for public. But how do some third party tools like Calibre Real Time is capable doing such (post edit) things. I can understand the ability of DRD/iPVS to do so. If this comes under some NDA you can say so. I can understand.

    -Ramakrishnan

  • in reply to RK56

    Hi Ramakrishnan,

    No, this is not available even under NDA. I cannot comment about what any third party might be doing.

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.