Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13254
  • 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

Determining if a custom toolbar exist

J Wilwert

Hi,

I am working in cadence 6.1.5.  I am creating and revising custom tool bars in the virtuoso environment.  How, using skill functions, can I determine if a custom toolbar exist in the window, so I can delete it before revising it?  I am hungup in evaluating the expression:

hiGetWindowToolbars(hiGetCurrentWindow()).  It returns a list of "something" of which I am struggling with.  Any ideas?  HELP!!

Many THANKS! in advance,

John Wilwert

  • Hi John,

    I would think that you need to pass the session window id to the hiGetWindowToolbars function?

    hiGetWindowToolbars(hiGetSessionWindow(hiGetCurrentWindow()))
=> (deGoToolbar_3 deBookmarksToolbar_3 deWorkspacesToolbar_3 leToolboxToolbar1_3
   leToolboxToolbar2_3 leFileToolbar_3 leEditToolbar_3 leAlignToolbar_3
   leViewToolbar_3 leCreateToolbar_3 ...

    You can use a function like member to see if a specific toolbar is a member of the list, or a combination of a setof filter which uses a rexMatchp function to test the name of the toolbar against a pattern (useful in this case as all of the toolbar items have a unique name).

    I hope that this is helpful.

    Lawrence.

  • Hi Lawrence,

    Thanks for the quick reply!! 

    I tried your suggestion of : hiGetWindowToolbars(hiGetSessionWindow(hiGetCurrentWindow())), and my custom toolbar was not included in the list!  So, I think I will continue to use the command I had been using.

    Nevertheless,  the part I am struggling with is in the using of the functions you suggested - member, setof, rexMatchup - in the testing of the pattern.  I'm getting tripped up in the syntax somewhere. Can you give a hint or two?

     

    Thanks,

    John Wilwert

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.