On 02/05/2018 11:38, Markus Armbruster wrote: >>>> It probably is not unless someone adds properties in realize() callback, >>> Now work that into the doc comment, please :) >> Are there any examples? > There must be examples where instances of the same type have different > properties, or else our design decision to create properties dynamically > was inane.
Buses for example create properties at runtime to link a parent to its children. These properties are created when a child device appears; this is different from creating properties in or the realize() callback, or upon setting other properties. The purpose of this command is to tell people/tools what they can pass to -device/-object/device_add/object_add, so the real question is whether there are cases where it falls short of that purpose. If not, maybe the wording for the .json file could be something like: Objects can create properties at runtime, for example to describe links between different devices and/or objects. These properties are not included in the output of this command. Paolo
