Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 15427
  • 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

Call a function after the user has selected something in the schematic editor

PatrikOsgnach

Hello,

I have a simple matter to solve. I would like to have a function called when the user selects something in the schematic editor.
In particular, whenever the user click on a wire, I'd like to call a function f(wire) that does something with the wire label.

How can I do this? I didn't find anything suitable in the function trigger names table.

BTW, is it possible to have a function called when the user closes a tab or clicks on edit->hierarchy->return menu item?

Thank you.

Parents
  • Andrew Beckett

    Patrik,

    In the trigger function, you get told (via the disembodied property list passed in) what action was taken - whether it was a push or a pop (I forget the action names) - it's args->action if I remember rightly. Plus you can always call one of these functions:

    geGetHierMemInst(
    [ w_windowId ]
    )
    => l_list / nil
    Returns a list describing the hierarchy of instances that have been descended into or edited-in-place to arrive at the cellview in the window.

    geGetInstHier(
    [ w_windowId ]
    )
    => t_instance-hierarchy / nil
    Returns a string describing the hierarchy of instances that have been descended into or edited-in-place in the current window to arrive at the cellview in the window.

    geGetInstHierPath(
    w_windowId
    )
    => l_instance-hierarchy / nil
    Similar to geGetInstHier but returns additional information for mosaic instances.

    This function returns a list of list describing the hierarchy of instances that have been descended into or edited-in-place in the current window to arrive at the cellview in the window. The list contains the following information for each instance:

    (dbinst memInst row column)

    to tell you the current hierarchy location (so the system keeps track of the stack - you don't have to do it yourself).

    Regards,

    Andrew

Reply
  • Andrew Beckett

    Patrik,

    In the trigger function, you get told (via the disembodied property list passed in) what action was taken - whether it was a push or a pop (I forget the action names) - it's args->action if I remember rightly. Plus you can always call one of these functions:

    geGetHierMemInst(
    [ w_windowId ]
    )
    => l_list / nil
    Returns a list describing the hierarchy of instances that have been descended into or edited-in-place to arrive at the cellview in the window.

    geGetInstHier(
    [ w_windowId ]
    )
    => t_instance-hierarchy / nil
    Returns a string describing the hierarchy of instances that have been descended into or edited-in-place in the current window to arrive at the cellview in the window.

    geGetInstHierPath(
    w_windowId
    )
    => l_instance-hierarchy / nil
    Similar to geGetInstHier but returns additional information for mosaic instances.

    This function returns a list of list describing the hierarchy of instances that have been descended into or edited-in-place in the current window to arrive at the cellview in the window. The list contains the following information for each instance:

    (dbinst memInst row column)

    to tell you the current hierarchy location (so the system keeps track of the stack - you don't have to do it yourself).

    Regards,

    Andrew

Children
No Data

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.