Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15369
  • 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

How to get current session of an opened ADE Verifier view.

fatcat1206

Hi All

Does anyone know how to get the current session of an opened ADE Verifier view.

I check the manual, there are two commands to get the session info

  • verifGetActiveSession: here the lib, cell and view info need to be specifier.
  • verifGetAllActiveSessions: it returns all the active session.

So neither of them fit with my request :(

Besides, I have tried to apply "geGetEditCellView()" and "hiGetCurrentWindow()" to the opened ADE Verifier, but both of them return nil.
I assume the "ADE Verifier" is different a object type. Can someone gives a brief explanation for it?

Best Regards

Yi

Parents
  • fatcat1206

    Hi Andrew

    As mentioned in the cadence custom support, I have developed a script to load the "custom field" value.

    As "verifSetReqCustomFieldValue()" requires the session of Verifier, I'd like to use the session of currently opened (activated) "Verifier" for it.

    And then I plan to trigger this script via a bind key defined for "Verifier", so the user do not need to specified the lib, cell and view name of the "Verifier".

    You may see that I am still using the concept when I develop some script to deal with the "schematic", "adexl" etc.

    As you have pointed out the concept for the "Verifier" is changed, then my flow may not suitable for it anymore.

    To be honest, I even fail to assign a bind key for the "Verifier", and end up with a APP form which is called in CIW.

    Best Regards

    Yi

Reply
  • fatcat1206

    Hi Andrew

    As mentioned in the cadence custom support, I have developed a script to load the "custom field" value.

    As "verifSetReqCustomFieldValue()" requires the session of Verifier, I'd like to use the session of currently opened (activated) "Verifier" for it.

    And then I plan to trigger this script via a bind key defined for "Verifier", so the user do not need to specified the lib, cell and view name of the "Verifier".

    You may see that I am still using the concept when I develop some script to deal with the "schematic", "adexl" etc.

    As you have pointed out the concept for the "Verifier" is changed, then my flow may not suitable for it anymore.

    To be honest, I even fail to assign a bind key for the "Verifier", and end up with a APP form which is called in CIW.

    Best Regards

    Yi

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.