Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13560
  • 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

max toggle callback string too long

lrlsk

Hi Everyone,

Does anybody know what is the maximum limit  input for a callback list in hiCreateToggleField? I get the following error message in my virtuoso CIW .

*WARNING* toggle callback string too long, cannot execute

I've checked cdnsdoc but there was no mention regarding maximum string limit.

I am using virtuoso version 6.1.6-64b.500.13.2

Thank you in advance and regards,

lrlsk

Parents

  • lrlsk,

    It's the length of the callback string that is the problem (not the number of callbacks). If any callback string is longer than about 8k characters (it was a little lower than that in my experiments - I think there's some margin included) then you get this warning. I had a callback string which was 8177 chars long (8192 was definitely too long).

    This is because of some historical fixed length strings in some parts of the UI code.

    There really should be no need to have a callback string that long - instead put the lengthy code in a function definition, and call that function instead.

    Regards,

    Andrew.

Reply

  • lrlsk,

    It's the length of the callback string that is the problem (not the number of callbacks). If any callback string is longer than about 8k characters (it was a little lower than that in my experiments - I think there's some margin included) then you get this warning. I had a callback string which was 8177 chars long (8192 was definitely too long).

    This is because of some historical fixed length strings in some parts of the UI code.

    There really should be no need to have a callback string that long - instead put the lengthy code in a function definition, and call that function instead.

    Regards,

    Andrew.

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.