Enable the tooltip in CED Modeling to be populated with Windchill attributes

Hi @KristofTheeten 

Thank you for your question. 

It appears that your post has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Best regards,

This can be done by some LISP programming.

First of all have a look to some of lisp function PTC does provide out-of-the-box. And for sure the IKIT functions of the browser area.

The OOTB functions can be found here: 
C:\Programs\PTC\Creo Elements\Direct Modeling 20.8.1.0\personality\sd_customize\UWGM\uwgm_browser_views.lsp
Within that file there are a bunch of small utility function to handle browser nodes and Windchill attributes.

there are some commented sequences.  Pick them up and place them in a file
$USERCUSTOMIZEDIR/UWGM/uwgm_browser_views.lsp

enable those of your interest and get familiar with those. That file will be loaded automatically on module startup.

Now I recommend to write your own interrogator function to have your own display name (that is the name right to the icons). using the IKIT-function 

(sd-browser-add-interrogator ... :tree-display-name 'the-new-display-name-function) 

and your own new function.

That way you can e.g. display the windchill name and the windchill number directly in the structure browser ( as a replacement or in addition to the default name, as your function returns a string)  -- This works fine (it have been one of my earliest adaptions)

Then ..  in the same function you might call in addition the function to set the node description via 

(sd-browser-exec-cmd name:SET-OBJECT-DESCRIPTION “the-new-tooltip-string”)

Normally it is only planned to the the description ONCE the node is created, but hat way we can still change it. Be aware of performance issues when writing those function..

And be aware that Modeling likes to get unstable when those self written functions involved into the browser run into a  LISP error. So you should test it with small model first and write failure-safe functions. You should know what you are doing!