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

Hi Patrik,

To my knowledge the best way to do this would be to modify the Left-Click mouse bindkey so that it calls a function as well or instead of the default schSingleSelectPt().  Here's a brief example of what I am suggesting:

procedure(myFun()
  let( ((obj car(geGetSelSet())))
    when(obj~>objType=="line"
      println(obj~>net~>name)
    ); when
  ); let
); procedure

hiSetBindKey("Schematics" "None" "schSingleSelectPt() myFun()")

Now whenever a wire object is clicked directly (i.e. not drag-selected, for example), the wire name would be printed out in the CIW.

I'm not sure if there is a trigger for switching tabs (I presume that you mean design window tabs, e.g. in a schematic editor window). There may be a trigger for returning (perhaps related to dePop() ?) or you might redefine the Ctrl-E bindkey (and menu item) to run your own function in addition to, or as a wrapper around the schHiReturn() function.

Hope this helps.

Regards,

Lawrence.

Hello Lawrence,

thank you, I'll try your solution.

Essentially I have to do two things:

1) keep track of a "descent hierarchy". When the user opens the first schematic, push the cell name on a stack. When the user descends into a subcell with the descend command (which opens the cell in a new tab or in the current one), push the name of the cell on the stack. When the user returns (with the return command, with Ctrl+E or by closing the tab), pop the last cell name from the stack.

I have solved this by using the deRegUserTrigger function to call a function when the schematic editor is opened. If the current cell name is already in the second-from-top position on the stack, it means that the user has returned and I'll just pop the top of the stack. Otherwise, I push the cell name. It works fine, but I was wondering if there is a cleaner solution.

2) I need to keep an history of clicked wires names (click alone, not click and drag). When the user click on a wire, add the name to the list. When there are 2 names on the list, do some processing and the do what would have been done after an ordinary click

Best regards,

Patrik

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

Hello Andrew,

thank you, geGetHierMemInst does what I need.

Do you know if these is a way to create a "spreadsheet" ? Regarding the second think I need to do, I want that, every time the user clicks on two wires, their names are added to the spreadsheet (essentially, two columns and n rows). I was thinking of using a two list boxes but they are scrollable independently. If I am looking at element 34 on the first list box, element 34 of the second list box must be at the same position on screen.

Maybe I could use hiCreateReportField

You could add a context menu (Right Mouse Button menu) over the field and that could be used to remove the row. There is info on adding context menus in the documentation (i.e. cdnshelp).

Regards,

Andrew.