Else we can fail at the first fallback check in getConfigValue while
we still have the possibility to have the cbinded key available in
"me" (initial config).
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
if we use a component with cbind in a static declaration,
we do not want to traverse the 'config' property, as this can lead
to properties of base classes which produce errors on copying
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
allow to access sub elements of configuration items for binding.
E.g., if the following configuration is present:
foo: {
bar: true
}
one could do:
xtype: 'displayfield',
cbind {
value: '{foo.bar}'
}
[...]
This mirrors the abillity of ExtJS's 'bind', which can do this also.
Simple implementation mirroring the surrounding code.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
