'Cache' properties in Kiro plugin

[TimoDritschler]

Since the Kiro plugin only forwards all properties from and to the TANGO world, it does not actually hold any property values itself.
However, 'recording' is dependent on several values such as frames-per-second, roi-width, roi-height, sensor-width and so on.
Therefore, the Kiro Plugin somehow needs to buffer these properties locally. But if the property gets changed on the TANGO side by someone other than the Kiro Plugin itself, then the plugin is currently unaware of these changes which might lead to inconsistencies and undefined behavior.
A possible approach to this problem would be to use TANGOS Event System to get notifications every time a property changes and react to those changes accordingly.

[matze]

There might be some overlap with #13. But that's lingering around for almost a year now ;-)

[TimoDritschler]

Ah, yeah, you are right!
I will take this into consideration. Thanks for noticing!