• 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 use hiHighlightField() to highlight a particular...

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 16130
  • 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 use hiHighlightField() to highlight a particular field if the input is incorrect

Manikk0501
Manikk0501 over 10 years ago

Hi all,

                 I want to hightlight a particular field in a GUI with multiple tabs if the user input is incorrect(Let say it is a file input and the file name which user mentioned is not existing).

                 I added a ?modifyCallback function which has hiHighlightField() function. 

                 Command line is like this

                 hiHighlightField( Form->TabField->TabName 'Field 2 )

                 As per the intention, Field is hightlighted if the input is wrong, but i am getting an error in CIW as follows

                                     *Error* eval: not a function - 'Field

                                     *Error* car: Can't take car of atom - ERROR

                Can anyone let me know what I am missing here

Thanks and Regards,

Manikandan Kuzandhaivelu

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

    For anyone interested in the problem...

    From having seen the whole code, the issue was not with hiHighlightField() at all, but in the specification of the ?modifyCallback. The expectation is that ?modifyCallback is the name of the function, not a complete expression - and "hi" will add the arguments to the function call itself. If you specify a complete expression, the arguments will still be added, but these arguments will end up being seen as a second function call, with the name of the function being the quoted field name - hence the error.

    Unfortunately this shows that seeing the whole code is often important to understand bugs - they're not always where you might think they are...

    Regards,

    Andrew.

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

    For anyone interested in the problem...

    From having seen the whole code, the issue was not with hiHighlightField() at all, but in the specification of the ?modifyCallback. The expectation is that ?modifyCallback is the name of the function, not a complete expression - and "hi" will add the arguments to the function call itself. If you specify a complete expression, the arguments will still be added, but these arguments will end up being seen as a second function call, with the name of the function being the quoted field name - hence the error.

    Unfortunately this shows that seeing the whole code is often important to understand bugs - they're not always where you might think they are...

    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