ID 366537 - Tooltips of parameters and attributes incorrectly include names of pages in full parameter/attribute names

Problem summary:

The tooltip that appears for hovered parameters in the Parameters tab and for hovered attributes in the Attributes tab displays the full name of a parameter or attribute. This feature enhancement was introduced in Katana 3.0v1 under TP 81710:

• TP 81710 / BZ 39744 - When hovering over a parameter, attribute, project setting, or preference, a tooltip now appears (after a short delay), which may include the full name, help text, and attribute type of the respective item.

  When holding down the Ctrl key before hovering over a parameter, attribute, project setting, or preference, the tooltip that appears will also show all widget hints of the respective item, which can help in building and debugging custom parameter interfaces.

  As part of this feature enhancement, the behavior of clicking the label of a multi parameter, e.g. the label of the screenWindow parameter of CameraCreate nodes, has been changed: Previously, when clicking the label to expand the multi parameter, its label text was aligned roughly in the center of the Parameters tab, making it harder to collapse the parameter again. Now, the label text is aligned to the left, just like the text of group parameter widgets, making it possible to quickly expand and collapse multi parameters.

The feature enhancement was well received by customers, but the full name incorrectly includes the names of pages that a parameter or attribute may be a part of. This is misleading to users interested in accessing parameters or attributes by their full name from a scripting, programming, or AttributeSet context, which does not work with names of pages.

Steps to reproduce:

1. In the Node Graph tab, create a Material node and set its view and edit flags.
2. In the Parameters tab, click Add Shader and choose dl > Surface to add a 3Delight surface shader.
3. Set the dlSurfaceShader parameter to dl3DelightMaterial.
4. Expand the parameters underneath the dlSurfaceShader group, and expand the Base Layer and Reflection pages.
5. Hover over the Base Layer > Reflection > Reflectivity parameter and wait for the tooltip to appear.
   • Compare expected behavior and actual behavior.
6. In the Scene Graph tab, expand the entire scene graph, and select the /root/materials/Material location.
7. In the Attributes tab, expand the material.dlSurfaceShader group attributes, and expand Base Layer > Reflection, to reveal the Reflectivity attribute.
8. Hover over the Base Layer > Reflection > Reflectivity attribute and wait for the tooltip to appear.
   • Compare expected behavior and actual behavior.

Expected behaviour:

The tooltip in the Parameters tab displays the full name of the parameter as shaders.dlSurfaceParams.reflect_reflectivity.

The tooltip in the Attributes tab displays the full name of the attribute as material.dlSurfaceParams.reflect_reflectivity.

Actual behaviour:

The tooltip in the Parameters tab displays the full name of the parameter as Material.shaders.dlSurfaceParams.Base Layer.Reflection.reflect_reflectivity.

The tooltip in the Attributes tab displays the full name of the attribute as material.dlSurfaceParams.Base Layer.Reflection.reflect_reflectivity.

Workaround:

A parameter or attribute whose full name is to be obtained can be dragged into the command area of a Python tab, in order to display the actual full name of the parameter or attribute as part of the resulting Python code snippet.

Tested versions/platforms:

• 3.0v1 - Affected
• 3.0v4 - Affected

Customer version/platform:

3.0v4/Linux