Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14493
  • 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

Failed to load icon file while loading toolbars

RK56

Hi,

I'm looking for solution for this error

\w *WARNING* (DEBASE-102205):_deCreateToolbarItems: Invalid iconFile "/projects/..../toolbars/icons/gravity-nexus.png" in action item "Snap to nexus". Make sure iconFile exists.

I have created a Layout.toolbar file under ~/.cadence/dfII/toolbars/byApplication/Layout.toolbars. If I provide the absolute path for the icon file, it loads safely. When I provide a relative path or a link to icon file, then it fails to load. I also tried using simplifyFilename("relative path to icon file") in the Layout.toolbars file. Surprisingly, the link given to simplifyFilename is expanded properly and yet fails to load the icon file.

Version used: @(#)$CDS: virtuoso version ICADV12.3-64b 01/24/2018 13:05 

-Ramakrishnan

  • Hi Ramakrishnan,

    The documentation explains that the icon files are found by looking in the paths in the setup.loc for the file in the directory icons/24x24 - so put your gravity-nexus.png file in ~/.cadence/icons/24x24 and just specify "gravity-nexus.png" in the toolbar file. The simplifyFilename approach won't work because it's expecting a literal path rather than a SKILL expression.

    By the way, the preferred way nowadays to create toolbars or modify toolbars for existing applications is to use toolbar overlays - the toolbar manager can create these for you (via Options->Toolbars in the CIW, for example). This means you're not trying to maintain a copy of the standard toolbar file.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Andrew Beckett said:

    The documentation explains that the icon files are found by looking in the paths in the setup.loc for the file in the directory icons/24x24 - so put your gravity-nexus.png file in ~/.cadence/icons/24x24 and just specify "gravity-nexus.png" in the toolbar file. The simplifyFilename approach won't work because it's expecting a literal path rather than a SKILL expression.

    Actually, the simplifyFilename is evaluated and I can see the expanded path in the warning. Strangely it is not taken by the toolbar initialization program. I went through setup.loc and I prefer to store the icons at ./.cadence/icons/24x24/

    Andrew Beckett said:

    By the way, the preferred way nowadays to create toolbars or modify toolbars for existing applications is to use toolbar overlays - the toolbar manager can create these for you (via Options->Toolbars in the CIW, for example). This means you're not trying to maintain a copy of the standard toolbar file.

    If I follow the above method, how can I share this setup with others. With toolbar file approach, the task is simpler. Any advice here? I want to share my toolbars, menus and workspace with the rest of the team. To share the menus I have a menu file under ./menus/

    Thanks

    Ramakrishnan

  • in reply to RK56

    Hi Ramakrishnan

    You can distribute the files in exactly the same way. The toolbar manager creates the overlay file in ~/.cadence/dfII/toolbars/byApplication with files called (for example) Layout.overlay - so just as you can put Layout.toolbars in a location found via setup.loc, you can put Layout.overlay in the same places.

    So I disagree - toolbar files are not simpler - you have a UI to create toolbar overlay files, they only record the changes (and so you don't have to be so careful about getting out of sync with the released toolbars from Cadence), and the sharing mechanism is the same.

    Regards,

    Andrew.

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.