Extending Orocos ToolKitE

Hi,
I'm trying to use a custom types using the extending orocos real-time
toolkit procedure. However, I'm face to a problem, I have a taskContext
containing a variable number of properties and not able use
marshalling.loadProperties() because it creates propertybag instead of my
own custom type.

The loading with marshalling.readProperties() works fine when the property
of a custom type is already created, but I would like to use variable
number of a custom type property in my configuration file.

On Thu, Jun 4, 2009 at 19:14, Simon
Pelletier-Thibault<simon [dot] pelletiert [..] ...> wrote:
> Hi,
> I'm trying to use a custom types using the extending orocos real-time
> toolkit procedure. However, I'm face to a problem, I have a taskContext
> containing a variable number of properties and not able use
> marshalling.loadProperties() because it creates propertybag instead of my
> own custom type.
> The loading with marshalling.readProperties() works fine when the property
> of a custom type is already created, but I would like to use variable
> number of a custom type property in my configuration file.
> Does any-one have an idea?

It's a kind-of open issue... The properties are older than the type
system, that's
why they don't use all the information in there yet. I wonder even if it's not
the responsibility of the demarshaller to lookup the type field of the
struct and
rebuild the property using the type system...
(look at CPFDemarshaller.cpp::endElement::case TAG_STRUCT: the property 'prop'
added to the bag in there should be first checked if it has a known
type and then
composed again to a property of that type and *then* added to the bag)

It must be possible to add this feature, but I'm on a tight schedule right now.

Please add a bug report if you can't figure it out and want us to track it.