Stats

  • Locked Locked
  • Replies 7
  • Subscribers 128
  • Views 18228
  • 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

Save Display Information

keithd

 hi,

I don't use Virtuoso much, so this may be obvious to the power users, but when I exit Virtuoso (6.15) it always opens a "Save Display Information" dialog and accuses me of editing the way my layers appear, even if the only thing I've done is open the tool and then type 'exit' in the CIW.

 Does it do that because it is reading display info from a file other than display.drf?   Is there a way to suppress this dialog or a dotfile I need to look at/modify?

 

thanks

-keith

  • keithd

     nevermind.

     

    the problem appears be because I had a "drLoadDrf" command in my .cdsinit file.

  • dmay

    This form has always annoyed me as well. We setup the following trick to automatically cancel the form when we exit:

    procedure(myAutoCancelSaveDrfForm()
        when(hiGraphicMode()
            hiRegTimer("hiiSetCurrentForm('techSaveDrmForm) hiFormCancel(techSaveDrmForm)" 10)
            ;for some reason the form in 6.1 doesn't appear as soon as in 5.1.41, so it needs a longer delay
            hiRegTimer("hiiSetCurrentForm('techSaveDrmForm) hiFormCancel(techSaveDrmForm)" 30)
        )
    ) ;proc

    regExitBefore('MTstAutoCancelSaveDrfForm)

    Maybe some of the Cadence insiders have a better way to handle this, but this works for me.

    Derek

  • Andrew Beckett

    Derek,

    drLoadDrf() has a second (optional) argument. If you use:

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

    Then it won't ask you to save it if display characteristics are changed during the session. This is often called in the libInit.il in the technology library - so adding nil as the second argument is any easy fix.

    Andrew.

  • dmay

    Thanks Andrew. I looked at the various places in our code where drf files are loaded and half of them used the second argument. I have updated the rest to pass in nil as well. There are so many layers in this onion. ;-)

     Derek

  • Magistus

    The idea with the second argument does not work. I added

    drLoadDrf("./display.drf" nil)

    in my .cdsinit and the window still appears after I exit virtuoso. Based on Dereks idea I have done it in that way:

    procedure(myAutoCancelSaveDrfForm()
    hiRegTimer("hiiSetCurrentForm('techSaveDrmForm) hiFormCancel(techSaveDrmForm)" 0)
    )
    regExitBefore('myAutoCancelSaveDrfForm)

    Curiously a delay of 0 is enough!

  • Jing Tan

    Hi Magistus,
    If I only have a copy of the display.drf file in my home directory (where I always load my display file), adding drLoadDrf("./display.drf" nil) in cdsinit doesn't work.
    But, if I have a copy of display.drf file in my project directory (even I still load my display file from home directory), drLoadDrf("./display.drf" nil) works.
    Hope this solution works for you too. :-)
    Jing

  • Andrew Beckett

    Jing,

    If it's in your home directory, wouldn't you need to do drLoadDrf("~/display.drf") instead? Using ./display.drf will only work if it's in the working directory.

    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.