http://bugs.orocos.org/show_bug.cgi?id=1004

Summary: accessing PropertyBag values that are nested in a
service fails
Product: Toolchain
Version: master
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P3
Component: RTT
AssignedTo: orocos-dev [..] ...
ReportedBy: meyer [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

Created attachment 839
--> http://bugs.orocos.org/attachment.cgi?id=839
fixed ValueParser for PropertyBag properties that are owned by services

Values of PropertyBags that are properties of services are not accessible from
scripting or in the TaskBrowser as the ValueParser class tries to access the
properties of the owner instead. Without having looked too deep into scripting
I created a patch that seems to fix this issue.

I am not sure if it is good practice that services have their own properties,
attributes and data flow. I am using them to encapsulate functionality that is
used more than once in a TaskContext (e.g. a single PID controller service in a
controller TaskContext with multiple cascaded or parallel controllers). From
the manual and the output of the TaskBrowser I assume that services are mainly
intended to provide and request operation interfaces?

Best regards
Johannes