• 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 manuplate the customer gui in the skill script

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 142
  • Views 15797
  • 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 manuplate the customer gui in the skill script

acom
acom over 9 years ago

Hello ,

We have a customer defined gui which is written by skill. I simplify it as LAYguiForm() in the file LAYguiForm.il.

Then we would like to automatically fill-in the myGuiForm and make it do some related actions. I simplify it as LAYdo(string) in the file LAYdo.il.

 But don't know why it didn't work as intended if i do as method 1 in the CIW window after start virtuoso.The myguiForm will pop up. But it won't auto fill-in and execute the following function.

At the same time, it works well when i input the sentence one by one as method 2 in the CIW window like below.

Method 1: In the CIW, it won't work as intented.

load "LAYguiForm.il"

load "LAYdo.il"

LAYdo("HELLOWORLD")

Method 2: If i input the sentence one by one in CIW like below .It works normally.

In the CIW:

load "LAYguiForm.il"

string="HELLOWORLD"

LAYguiForm()

hiSetCurrentForm(myGuiForm)

myGuiForm->libName->value=string

hiFormDone(myGuiForm)

So my issue is , have i missed anything in the LAYdo.il file?How can make it auto fill-in and execute by using LAYdo.il?

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; In the LAYguiForm.il file     ;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

procedure( LAYguiForm()
let(
(stepBtn libName
)

stepBtn = hiCreateBooleanButton(
?name 'stepBtn
?buttonText "step1"
?buttonLocation 'left
?defValue nil
)

libName = hiCreateStringField(
?name 'libName
?prompt "Library Name"
?defValue ""
?enabled t
?callback "ddsUpdateSyncWithForm()"
)


myGui= hiCreateAppForm(
?name 'myGuiForm
?formTitle "mygui"
?callback "LAYmyGuiExe_(myGuiForm)"
?fields list(
list(stepBtn 15:22 20:15 0)
list(libName 15:81 275:25 105)
)
?initialSize t
)

hiDisplayForm(myGuiForm)
ddsEndSyncWithForm()
)
)


procedure( LAYmyGuiExe_(myGuiForm)
let(
(libName
)
libName = myGuiForm~>libName~>value
printf("the lib name is %s .\n" libName)
)
)

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;           In the LAYdo.il File       ;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

procedure(LAYdo(string)
let(
()
LAYguiForm()
hiSetCurrentForm(myGuiForm t)
myGuiForm->libName->value=string
hiFormDone(myGuiForm)

)
)

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    The other possibility is that you declared myguiForm as a local variable and were using that for your form object. If you have ?dontBlock t, the hiDisplayForm will return and it will no longer be in the context of where the form variable got created and hence you may have a scoping problem.

    Generally speaking, top level UI items (e.g. forms) should be stored in a unique global variable, not a local variable.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    The other possibility is that you declared myguiForm as a local variable and were using that for your form object. If you have ?dontBlock t, the hiDisplayForm will return and it will no longer be in the context of where the form variable got created and hence you may have a scoping problem.

    Generally speaking, top level UI items (e.g. forms) should be stored in a unique global variable, not a local variable.

    Regards,

    Andrew.

    • 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