Page MenuHome

data path for custom prop is wrong for info menu
Open, NormalPublic


System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67

Blender Version
Broken: version: 2.80 (sub 58), branch: master, commit date: 2019-04-21 20:30, hash: rB797539e76ccf
Worked: (optional)

Short description of error
When change custom prop value , the info show wrong path of custom properties

  1. open attached file.

2 .select armature > properties editor>custom properties> change value of "prop" as 0.7 etc

  1. open info menu. then check how it recorded. bpy.context.object.["prop"] = 0.7
  2. but bpy.context.object.["prop"] is wrong path. it should be bpy.context.object["prop"] , should not add "."

I do not know if it had been reprorted, because same thing happen about current 2.7 build.
and it is only annoying for new user who try to use info , as same as T63686
hope all these missing path will be corrected. (actually I thought if API change about custom property too,,)



Event Timeline

takeshi funahashi (waitinfuture) renamed this task from path for custom prop data path is wrong for info menu to data path for custom prop is wrong for info menu.Apr 22 2019, 8:39 AM
takeshi funahashi (waitinfuture) updated the task description. (Show Details)

You have an extra . it's bpy.context.object["prop"] or bpy.context.object.prop

Edit: I misread sorry, I can confirm the issue

Yes as you said. bpy.context.object["prop"} is right. then I do not complain about it you already notice. the problem is info window record wrong path.
And thanks confirm. Then It is for user who try to learn bpy with blender bpy documents. But I have not thought there is case , info show wrong path.

Philipp Oeser (lichtwerk) triaged this task as Normal priority.Apr 23 2019, 2:17 PM

Confirmed, checking... [think this is isolated to the Info Editor though...]

note: its also not reporting the right object if an object is pinned [will always output bpy.context.object]

Thanks. I think, this happen about all custom property. context.scene.[prop] , context.object.active_material.[prop],["prop"] etc.