Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14605
  • 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

load different display by a hot key

enzhu

Hi All,

There is a default display file from foundry and don't want to modify directly. But would like to use a different display file to load some personal settings. Can we define a short cut key to switch between two display files? 

Thanks. 

ELiang

Parents
  • Andrew Beckett

    Use drLoadDrf("/path/to/display.drf" nil)

    The nil as second argument means it won't ask you to save it when you quit virtuoso (can be a bit annoying otherwise).

    Andrew.

  • enzhu
    in reply to Andrew Beckett

    Hi Andrew,

    Just got a chance to try it. I am trying to make a dis.il file (and load it in CIW or init file later). But I got syntax errors by putting the following lines into the dis.il file:

    hiSetBindKey( "Schematics" "<Key>k" "drLoadDrf("/home/andy/display.drf" nil)") ;hiSetBindKey
    hiSetBindKey( "Schematics" "Shift<Key>k" "drLoadDrf("/home/andy/display_thick.drf" nil)") ;hiSetBindKey

    What I am trying to make is to use k to use thin line; K for thick line during schematic highlights. 

    Could you please help to take a look at this? 

    Thanks .

    ELiang

  • Andrew Beckett
    in reply to enzhu

    You need to escape the embedded quotation marks:

    hiSetBindKey( "Schematics" "<Key>k" "drLoadDrf(\"/home/andy/display.drf\" nil)") ;hiSetBindKey
    hiSetBindKey( "Schematics" "Shift<Key>k" "drLoadDrf(\"/home/andy/display_thick.drf\" nil)") ;hiSetBindKey

    Otherwise it will see the bind key string as ending after the 'drLoadDrf(' bit and then the rest would cause a syntax error because there's no space. Escaping the quotation marks needed as part of the call to drLoadDrf means that the entire command is defined as the bind key.

    Regards,

    Andrew.

Reply
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.