• 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. Allegro X PCB Editor
  3. Why form's select CHECKLIST cannot work within tab

Stats

  • Replies 1
  • Subscribers 160
  • Views 733
  • Members are here 0
More Content

Why form's select CHECKLIST cannot work within tab

Evel Liu
Evel Liu over 16 years ago
I just do a little form for two kinds action on the different chose. but can not work for this code, what happen with it? for example, chose a tab and then chose a_select1, action A1 chose b tab and then chose b_select2, action B2 code for ================== (defun _select_callback (form) (case form->curValue ("a" print("select a tab\n") if(form->curField=="a_select1" axlUIWPrint(form "Get a_select1 value!") ) ) ("b" print("select b tab\n") if(form->curField=="b_select2" axlUIWPrint(form "Get b_select2 value!") ) ) ) ) =============
  • Sign in to reply
  • Cancel
  • aCraig
    aCraig over 16 years ago

    Evel,

    I'm assuming here that a/b are tabs and a_select1 is field on tab a and b_select2 is a field on tab b. 

    Everytime you click (or double click) in a form is one trip through your "call_back" function. So when you select tab "a", your "call_back" function is executed, when you enter something in field "a_select1" your "call_back" function is executed. Your code only checks to see if the tabs have been selected in the case statement. So when you enter something in one of the fields there is no check in the case statement for it. You should check for the curField in the case statement. In most cases you really don't care which tab you are on.

    Hope that helps.

    -Craig

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Cadence Guidelines

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