• 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. automatic setIconName ?

Stats

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

automatic setIconName ?

yeh1
yeh1 over 8 years ago

Is there a way in skill to force the icon name to "lay" for a layout window and "sch" for a schematic window?  Maybe some userPostInstallTrigger is needed?  hiSetIconName(getCurrentWindow() "sch") works manually but when I descend/return in hierarchy, the icon name reverts to the cellname, in the gnome taskbar (window selector).  Having a short name "lay" or "sch" makes it easier for me to identify the window in the taskbar, since I use one tabbed session window for layout and another for schematic.  Thanks.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I normally use KDE so that doesn't use the icon name (I'd have to restart with Gnome to test), but by just checking what hiGetIconName(hiGetCurrentWindow()) returns, I think this will work:

    procedure(CCFsetIconName(args)
      hiSetIconName(args->window
        case(args->viewType
          ("maskLayout" "lay")
          ("schematic" "sch")
          ("schematicSymbol" "sym")
          (t args->cellName) ; the default
        )
      )
    )

    deRegUserTriggers("schematic" nil nil 'CCFsetIconName)
    deRegUserTriggers("schematicSymbol" nil nil 'CCFsetIconName)
    deRegUserTriggers("maskLayout" nil nil 'CCFsetIconName)
    deRegUserTriggers("maskLayoutXL" nil nil 'CCFsetIconName)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yeh1
    yeh1 over 8 years ago
    That works, perfect, thanks!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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