• 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. calculated value in ?headers of hiCreateReportField

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 13839
  • 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

calculated value in ?headers of hiCreateReportField

The Consultant
The Consultant over 12 years ago

Hi,

i creat a form with an report field. The value in the header should not a fixed value in the code, it should be a varialbe.

but i get an error, fixnum req.

 

here is the code

------------------------------------------------

width = 30x ( some digit)

reportField = hiCreateReportField(
        ?name       'reportField
        ?title      "Report"
        ?selectMode 'multiple
        ?headers    '(
                       ("obj-type"     75   'left)
                      ("l"            75   'left)
                      ("pp"           75   'left)
                      ("description"  width   'left)
                      )
        ?choices     ch
)

-----------------------------------------

 

 if i change with to e.g. 100 , everything is fine.

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

    If you use '(...) the list is quoted which means that nothing is evaluated inside the list. You have a couple of choices:

            ?headers    list(
                          list("obj-type"     75   'left)
                          list("l"            75   'left)
                          list("pp"           75   'left)
                          list("description"  width   'left)
                          ) 

    Or you could use the backquote approach which allows selective evaluation of things preceded by a comma (note the 'left will be quoted - so don't really need the quote either):

            ?headers    `(
                          ("obj-type"     75   left)
                          ("l"            75   left)
                          ("pp"           75   left)
                          ("description"  ,width   left)
                          ) 

    Sometimes the backquote approach is cleaner because it is clearer when you are just inserting a small number of values into an otherwise static list structure. It's actually a macro which expands into list() (and other function calls).

    Regards,

    Andrew.

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

    If you use '(...) the list is quoted which means that nothing is evaluated inside the list. You have a couple of choices:

            ?headers    list(
                          list("obj-type"     75   'left)
                          list("l"            75   'left)
                          list("pp"           75   'left)
                          list("description"  width   'left)
                          ) 

    Or you could use the backquote approach which allows selective evaluation of things preceded by a comma (note the 'left will be quoted - so don't really need the quote either):

            ?headers    `(
                          ("obj-type"     75   left)
                          ("l"            75   left)
                          ("pp"           75   left)
                          ("description"  ,width   left)
                          ) 

    Sometimes the backquote approach is cleaner because it is clearer when you are just inserting a small number of values into an otherwise static list structure. It's actually a macro which expands into list() (and other function calls).

    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