• 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 update the List Box Field when its value has been...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 17013
  • 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 update the List Box Field when its value has been changed with another callback function

fatcat1206
fatcat1206 over 9 years ago

Hi All

I have created a "list box field" for a list of pin names, in a callback function of a form button, I have removed some items from the list, somehow the selection in the "list box field" does not change accordingly.

I check the value of "list box field", it has been changed, just the field itself has not been updated.

It's quite strange that when I assign the value of "list box field" in the CIW, the selection in the "list box field" dose change.

below is my callback fucntion, and "fPinInfoSel" is the listBoxField.

Does anyone knows where is wrong?

procedure(fFilterButtonCB(form)
let(
(
    DeSelPinKeyWordList           ;list of key words for deselected pin
    pinNameList                            ;an operation list
);local variable
    DeSelPinKeyWordList = parseString(SISpinInfoSelForm->fDeSelPinKeyWord->value)
    
    pinNameList = form->fPinInfoSel->value
    
    foreach(DeSelPinKeyWord DeSelPinKeyWordList
        foreach(pinName pinNameList
            when(rexMatchp(DeSelPinKeyWord pinName)
                remd(pinName pinNameList)
            );when
        );foreach pinName
    );foreach
    
    form->fPinInfoSel->value = pinNameList
    
);let
);proc

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

    One should always be careful when using destructive operators on lists - you have to know exactly how other consumers of the same list are using the data to know whether they might be impacted. If you are responsible for creation of the list and all operations on the list, then it's under your control and you can take advantage of the efficiency improvements that destructive operators can give you.

    Regards,

    Andrew

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

    One should always be careful when using destructive operators on lists - you have to know exactly how other consumers of the same list are using the data to know whether they might be impacted. If you are responsible for creation of the list and all operations on the list, then it's under your control and you can take advantage of the efficiency improvements that destructive operators can give you.

    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