[Rock-dev] Regarding dynamic properties

[Matthias Goldhoorn]

They are quite stables so far, expect:
they are in the end thought orocos.rb RPC (operations) on the task.
The problem here is if, the underlying task is not (yet) running the 
often setting something on not-yet initialized members. This could be 
checked within the task, but i still find this ugly.

I would prefer that:
- the operation get's called if the task was already configured
- the normal property get's set if the task is not (yet) configured
- Syskit get's hang if the operation is called

Each user then (which is normally the case) has to check during 
configuration time the value of the property.

Thoughts?

-- 
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 1
  28359 Bremen, Germany
  
  Zentrale: +49 421 178 45-6611
  
  Besuchsadresse der Nebengeschäftstelle:
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Tel.:    +49 421 178 45-4193
  Empfang: +49 421 178 45-6600
  Fax:     +49 421 178 45-4150
  E-Mail:  matthias.goldhoorn at informatik.uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik