• 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. IC 6.14: How to write to the status line of a edit-window...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 143
  • Views 15087
  • 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

IC 6.14: How to write to the status line of a edit-window?

StefanSL
StefanSL over 14 years ago

 Dear all,

i'm desperately looking for a possibility to write commands or status messages to
the status line of a design window, but without luck until now, neither the documentation
nor this forum were very helpful;

currently i'm writing output to the user  to the CIW, but i'm not happy with that cause
quite often you don't have the CIW directly in your field of vision, so my users have been
waiting for something to happen whilst virtuoso was waiting for some input...

 any possibility to put my messages to the status line of the design window?

thanks for your help

Stefan

  • Cancel
Parents
  • StefanSL
    StefanSL over 14 years ago

    the problem i've mentioned above is as follows:

    when setPrompts() is run manually, from the CIW, the prompt will follow the
    command  without any delay; if i run my script repeatedly, the prompt
    seems to remain unchanged although i set it to the desired output and
    afterwards i set it back to "" or ">".

    In fact, the prompt is changed but not shown immediately, the change
    becomes visible when the user interacts with the design window;
    cause i want to use this message as a command to the user, this approach
    is not sufficiently reliable, i should stay with Andrews proposal to use
    hiChangeBannerLabel()...

    kind regards, many thanks for your support

    Stefan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StefanSL
    StefanSL over 14 years ago

    the problem i've mentioned above is as follows:

    when setPrompts() is run manually, from the CIW, the prompt will follow the
    command  without any delay; if i run my script repeatedly, the prompt
    seems to remain unchanged although i set it to the desired output and
    afterwards i set it back to "" or ">".

    In fact, the prompt is changed but not shown immediately, the change
    becomes visible when the user interacts with the design window;
    cause i want to use this message as a command to the user, this approach
    is not sufficiently reliable, i should stay with Andrews proposal to use
    hiChangeBannerLabel()...

    kind regards, many thanks for your support

    Stefan

     

    • 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