# Add property path to controls in the Inspector

**URL:** <https://forum.babylonjs.com/t/add-property-path-to-controls-in-the-inspector/34401>\
**Category:** Feature requests\
**Tags:** inspector, control, ui\
**Created:** [October 2, 2022, 7:48am UTC](https://forum.babylonjs.com/t/add-property-path-to-controls-in-the-inspector/34401 "2022-10-02T07:48:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dok11](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/dok11/32/25754_2.png) [@Dok11](https://forum.babylonjs.com/u/Dok11)\
**Post date:** [October 2, 2022, 7:48am UTC](https://forum.babylonjs.com/t/add-property-path-to-controls-in-the-inspector/34401/1 "2022-10-02T07:48:19Z")

</div>

When I changed some property in the Inspector I want to know which property I schould change in my code to have the same effect.  
It will helpful to have at least tooltip near the label of control.

For example, I tune the “Bump strength” and I dont know what is this property. So currently I search label text in the repository and got this code:

```auto
<SliderLineComponent
  lockObject={this.props.lockObject}
  label="Bump strength"
  target={material.clearCoat.bumpTexture}
  propertyName="level"
  minimum={0}
  maximum={2}
  step={0.01}
  onPropertyChangedObservable={this.props.onPropertyChangedObservable}
  />

```

Finally, I know that correct property path is `material.clearCoat.bumpTexture.level`.

But if we have that path in the label then I should not go to github search. For example:

```auto
<SliderLineComponent
  label="Bump strength (material.clearCoat.bumpTexture.level)"
  ...

```

For example, look how it made in the Blender, every control has tooltip for python path to the propery:  
 ![image](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/3X/7/b/7b2e399f68308c20ae5c68272ed4a4ae29b9ec61.png)

And more, we even can copy that path here:

 ![image](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/3X/d/9/d956ba137be0ed738fe36fa2b5c6c157f38626ff.png)

---

<div class="post-metadata">

**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\
**Post date:** [October 3, 2022, 12:49pm UTC](https://forum.babylonjs.com/t/add-property-path-to-controls-in-the-inspector/34401/2 "2022-10-03T12:49:41Z")

</div>

They might not all be as straightforward unfortunately. You could rely on the scene recorder to directly create the code delta you would need.

Adding @RaananW to see what he thinks as well.

---

<div class="post-metadata">

**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\
**Post date:** [October 4, 2022, 9:56am UTC](https://forum.babylonjs.com/t/add-property-path-to-controls-in-the-inspector/34401/3 "2022-10-04T09:56:09Z")

</div>

I agree with both - it will be nice to have it, but it’s not so straightforward. And the change recorder could provide better experience than searching the code, that’s for sure.  
The reason i personally think it’s not that straightforward is that the inspector didn’t always change the base object’s variable directly. Sometimes it’s an object that is a member of the specific class, sometimes we have constants or enums. The general UX will probably not be consistent.  
Also not sure a tooltip will be the best option here. Maybe @PatrickRyan can pitch in for a good way to show the property name.

But in general, i like this suggestion. Maybe we can combine it with some form of a live display of the scene recorder, so you can see what variable was changed during a recording?