Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 15528
  • 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

VLS lock manager auto-refresh without DM

caver456

Hello - we're trying to write a lock manager which shows the user what cells are currently write-locked in a certain library, by whom, and when the lock was created.  We've got most of this in place already, including an option to release the write lock on a cell that you yourself have write-locked.

We are not using any Design Management system - just a plain-ol OA library on disk that multiple people point to.

As it is now, you have to manually refresh the locked file listing by clicking a button in the lock manager GUI.  It would be excellent to get rid of that need: is there a good way to have the lock manager automatically refresh whenever a locked cell becomes unlocked, or when a previously unlocked cell gets locked by any user running on any node?

ddRegTrigger("PreObjAccess" 'stuff) works for a single user's session; you would have to make sure that each user is running that trigger (and its callback function) and you'd also have to work some form of IPC to get them to notify each other of changes.

Linux has some options like 'watch', which could also push out to all IPC listeners and would only have to run on one node, but it would be nice to not have a constantly running background application - but maybe it's not that computationally expensive?

Is there some lower-level linux file system trigger that sends notifications on file/dir changes, which IPC could listen for, or even better, is there actually an already-existing SKILL function to do said listening?

What's your recommended course of action for this type of listening?

Thanks

Parents
  • dmay

    We did something like this and we simply used hiRegTimer to check at a given frequency and update the form. If the action is very fast and lightweight this won't cause any issues and is the easiest way to keep a form refreshed. hiRegTimer tells Cadence to run a skill command some amount of time in the future. In 60 seconds it can refresh the form and then issue the next hiRegTimer.

    Derek

Reply
  • dmay

    We did something like this and we simply used hiRegTimer to check at a given frequency and update the form. If the action is very fast and lightweight this won't cause any issues and is the easiest way to keep a form refreshed. hiRegTimer tells Cadence to run a skill command some amount of time in the future. In 60 seconds it can refresh the form and then issue the next hiRegTimer.

    Derek

Children
  • Andrew Beckett
    in reply to dmay

    In addition to Derek's comments, you might also find my little package which creates a simple interface around hiRegTimer to schedule repeating jobs useful: How to schedule a repeating function with a timer in SKILL?

    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.