Stats

  • Locked Locked
  • Replies 8
  • Subscribers 149
  • Views 4849
  • 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

Trigger on Select/Unselect

J Wilwert

Hi,

I am new to the concept of triggers and haven't been able to spend a lot of time doing any detailed research - so right to the point.

I want to execute a bit of skill code when an item is selected/deselected.  Can this be done with the use of a trigger?  Is there an other approach which might be better?  Any ideas anyone?

 Many THANKS in advance,

John Wilwert 

Parents
  • dmay

    We have used the triggers Ted mentioned in his post as well as a wrapper for the left click bindkey as suggested by Lawrence. For what its worth, here is what we do:

    The wrapper code around the left mouse button will print information to the ciw about the selected item. If it is a rectangle, it will print the layer, width, length and area.  For paths it prints the width, length and layer. For instances it prints the library name, cell name, instance name and xy location. For pcells, various parameter values are printed. This allows a user to get the most commonly used information without having to query the object.

    We registered a skill function with the leRegUserObjectSelectionFilter to determine whether or not an instance should be selectable. We created a user interface to allow designers to lock down cell placements. Once a cell placement is locked, you cannot select that cell (based on the trigger code we wrote). This allows us to significantly reduce those inadvertant cell movements that can wreak havoc on a design before they are discovered. We used to run into problems when routing cells might shift by a small amount and we found out hours later that many connections were mis-aligned. This trigger has saved us many hours of rework.

    Derek

Reply
  • dmay

    We have used the triggers Ted mentioned in his post as well as a wrapper for the left click bindkey as suggested by Lawrence. For what its worth, here is what we do:

    The wrapper code around the left mouse button will print information to the ciw about the selected item. If it is a rectangle, it will print the layer, width, length and area.  For paths it prints the width, length and layer. For instances it prints the library name, cell name, instance name and xy location. For pcells, various parameter values are printed. This allows a user to get the most commonly used information without having to query the object.

    We registered a skill function with the leRegUserObjectSelectionFilter to determine whether or not an instance should be selectable. We created a user interface to allow designers to lock down cell placements. Once a cell placement is locked, you cannot select that cell (based on the trigger code we wrote). This allows us to significantly reduce those inadvertant cell movements that can wreak havoc on a design before they are discovered. We used to run into problems when routing cells might shift by a small amount and we found out hours later that many connections were mis-aligned. This trigger has saved us many hours of rework.

    Derek

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.