Right now there seems to be limited support for programmatically traversing hierarchically nested introspection Node trees as doing so currently requires iteration over all interfaces and then all methods/signals/properties in each interface, adding the ability to do name key index based look-ups for both interfaces and their methods/signals/properties is something I've been experimenting with in #105.
One of the reasons for this is to make it possible to fully track a hierarchical object along the lines of an objectmanager but with auto-binding to the required InterfacesAdded, InterfacesRemoved and PropertiesChanged signal notification interfaces so that we can track interface/property changes in those objects fully.
Right now there seems to be limited support for programmatically traversing hierarchically nested introspection Node trees as doing so currently requires iteration over all interfaces and then all methods/signals/properties in each interface, adding the ability to do name key index based look-ups for both interfaces and their methods/signals/properties is something I've been experimenting with in #105.
One of the reasons for this is to make it possible to fully track a hierarchical object along the lines of an objectmanager but with auto-binding to the required
InterfacesAdded,InterfacesRemovedandPropertiesChangedsignal notification interfaces so that we can track interface/property changes in those objects fully.