• 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. Form popup from library manager causes library manager to...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14581
  • 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

Form popup from library manager causes library manager to wait...

markbeck
markbeck over 13 years ago

Greetings all,

I'm running Virtuoso IC6.1.5.500.7

I've got a form which is launched from the library manager which works fine, except that when the form is launched it causes the library manager to wait (busy cursor) while the form is up.  If I close the form, it returns control to the library manager. 

I know it's possible to spawn a form from the library manager without causing it to wait since the copy form doesn't freeze the lib manager. 

Any ideas out there?

Mark

  • Cancel
Parents
  • markbeck
    markbeck over 13 years ago

     Hi Lawrence,

    It is a form that I am creating on my own with the cdsLibMgr.il file.  I hadn't used the ?unmapAfterCB option, so it should have been unmaped once the form was created.   Here's a code snippet to see what I was doing:

    ; In cdsLibMgr.il
    lmgrCreateMenuItem("Test" "simple"
                           '(("label" "Run Test")
                             ("callback" ("Test_CB"))
                            ); list
                          ); lmgrCreateMenuItem

    lmgrAddMenuItems("MyToolsMenu" "LCV" (list "Test"))

    ; Defined in a .cdsinit file
    (defun Test_CB (@rest l_args)
      (let ( g_form buttonField)
        ;--------------------------------
        ;Main Code
        ;--------------------------------
        buttonField = hiCreateButton( ?name 'someButton
          ?buttonText "More Options"
          ?callback "printf(\"pressed\")" )

          g_form = hiCreateAppForm( ?name 'myForm
            ?formTitle "formName"
            ?fields list( buttonField)
            ?callback "printf(\"Done!\\n\")"
            ?unmapAfterCB nil
          )
          hiDisplayForm(g_form)
      ); let
    );

    If you launch the test form, it works fine, but when you try and access the library manager while the form is up, it is still waiting.

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • markbeck
    markbeck over 13 years ago

     Hi Lawrence,

    It is a form that I am creating on my own with the cdsLibMgr.il file.  I hadn't used the ?unmapAfterCB option, so it should have been unmaped once the form was created.   Here's a code snippet to see what I was doing:

    ; In cdsLibMgr.il
    lmgrCreateMenuItem("Test" "simple"
                           '(("label" "Run Test")
                             ("callback" ("Test_CB"))
                            ); list
                          ); lmgrCreateMenuItem

    lmgrAddMenuItems("MyToolsMenu" "LCV" (list "Test"))

    ; Defined in a .cdsinit file
    (defun Test_CB (@rest l_args)
      (let ( g_form buttonField)
        ;--------------------------------
        ;Main Code
        ;--------------------------------
        buttonField = hiCreateButton( ?name 'someButton
          ?buttonText "More Options"
          ?callback "printf(\"pressed\")" )

          g_form = hiCreateAppForm( ?name 'myForm
            ?formTitle "formName"
            ?fields list( buttonField)
            ?callback "printf(\"Done!\\n\")"
            ?unmapAfterCB nil
          )
          hiDisplayForm(g_form)
      ); let
    );

    If you launch the test form, it works fine, but when you try and access the library manager while the form is up, it is still waiting.

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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