• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. How to attach a menu to VXL

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13085
  • 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 attach a menu to VXL

venuuuuu
venuuuuu over 13 years ago

 hi all,

1) I have a code to attach pulldown menu to the VLE. Now i need to attach to add this menu to my VXL . How can i do it?

2)I don't  use of turbo toolbox. Can any one explain about it

 

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago
    1. This can be done two ways:
      1. Use the menus file mechanism; See <ICinstDir>/tools/dfII/etc/tools/menus and there's a README file in there
      2. Use the deRegUserTriggers function to define a user menu trigger (which returns a list of pulldown menus) for the Layout XL application. I can't remember off the top of my head (I'm not at work) what the right name is (think it might be maskLayoutXL or similar), but you should be able to use deGetViewType(hiGetCurrentWindow()) to return the name of the vie. It's either than or use hiGetAppType(hiGetCurrentWindow()) - sorry for not being precisel. Anyway, I'm sure you can figure it out.
      Since you didn't say how your existing code works, it's hard to know what to advise.
    2. This is covered in the documentation, which would be worth reading before asking questions to the forum. It's there for a reason...
      If you can't find it (it's in cdsdoc or you can just look in the pdfs in the <ICinstDir>/doc dir), it's here.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • venuuuuu
    venuuuuu over 13 years ago

    Thank you  Andrew for doing help on attach a menu to VXL. I got it. For turbo toobox(5141) I have much doubts.

    1) i change the library name in the rule file in your_install_dir/tools/dfII/samples/leToolbox and save it my current directory. When i run Edit contact option then CIW shows

     _leTbCommand( "_leTbEditContact()" )

     _leTbEditContact() _leTbRefreshMousePrompts( hiGetCurrentWindow() nil ) hiRedraw()

     *Error* (tb000067): The cdsVia "M2_M1c" is not defined properly.

     The parameters ("layer1XDefOverride" "layer1YDefOverride" "layer2XDefOverride" "layer2YDefOverride") are not defined in the techfile.

     What is the problem. Is there any change is need in rule file?

    2) what is the meaning of  leTbRules->ndiff_layer = '( "Oxide" "drawing" ) . I dont know what is  Oxide layer.

    3) When i minimize the Turbo Toolbox icon menu then it never Appears in next time.

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    I'd suggest you contact customer support over this. I presume you've changed more than just the library name in the rules file as there are quite a few settings which are technology specific. For your second question, the "Oxide" layer is the name of the active (diffusion) layer in the gpdk090 technology - it is probably called something else in your technology. 

    I don't know what you mean by the third question. So asking customer support is probably the best bet.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information