• 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 let a hiCreateStringField to type in a string then...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 1673
  • 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 let a hiCreateStringField to type in a string then launch its callback and the hiCreateAppForm won't be disappear ?

Charley Chen
Charley Chen over 8 years ago

Hi All,

When I type in a string in the hiCreateStringField and press enter , but the  hiCreateAppForm is disappered ,

I want to launch the callback of hiCreateStringField .

hiCreateAppForm(

?name 'myform

?buttonLayout  'Close

?unmapAfterCB t

.

Thank you,

Charley

.)

  • Cancel
Parents
  • skillUser
    skillUser over 8 years ago

    Hi Charley,

    The "Enter" key is bound to the same action as the first button, usually OK, it is a form key not a field-specific key. Here is a section from the documentation on this:

    Enter: Pressing Enter, <Enter>, performs the same action as the first button of the form button list. This is usually hiFormDone() for non-options forms and hiToggleEnterForm() for options forms. If you specify your own button list, you need to be aware that the action of <Enter> will change. For example, if your button list is


    'ApplyCancelDef, the action of <Enter> in a type-in field performs the hiFormApply() action.

    You can also customize this feature by specifying the button that you want to link to Enter. You do this setting the following environment variable in your .cdsenv file:

    ui formDefaultAction string "value"

    where value is the buttonText of the button that you want to link to <Enter>.

    When this variable is set, the g_buttonLayout argument is searched for the button whose text equals the value of the variable. The first button that is found becomes the default button.

    If the specified value is not found in g_buttonLayout, then <Enter> performs the same action as the first button of the form button list.

    Hopefully this helps you.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 8 years ago

    Hi Charley,

    The "Enter" key is bound to the same action as the first button, usually OK, it is a form key not a field-specific key. Here is a section from the documentation on this:

    Enter: Pressing Enter, <Enter>, performs the same action as the first button of the form button list. This is usually hiFormDone() for non-options forms and hiToggleEnterForm() for options forms. If you specify your own button list, you need to be aware that the action of <Enter> will change. For example, if your button list is


    'ApplyCancelDef, the action of <Enter> in a type-in field performs the hiFormApply() action.

    You can also customize this feature by specifying the button that you want to link to Enter. You do this setting the following environment variable in your .cdsenv file:

    ui formDefaultAction string "value"

    where value is the buttonText of the button that you want to link to <Enter>.

    When this variable is set, the g_buttonLayout argument is searched for the button whose text equals the value of the variable. The first button that is found becomes the default button.

    If the specified value is not found in g_buttonLayout, then <Enter> performs the same action as the first button of the form button list.

    Hopefully this helps you.

    Regards,

    Lawrence.

    • 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