On 12/11/2013 02:14 PM, Matthias Goldhoorn wrote: > Dynamic properties were introducer where --- during runtime a > configuration change is allowed > For a Servo if your change your system design you might during runtime > change some allowed ranges. That's true. However, it does not explain why *in this case*, doing so with a dynamic property would be better than with task reconfiguration
As Alex pointed out, dynamic properties have a cost on the component implementation's complexity as well as on compilation times. I personally feel that we should restrict them to the cases where it really makes sense. Exposure on a camera ? Makes sense ! You want to do be able to do dynamic exposure. Or maybe a port would be better there ? Maximum speed on a servo ? I personally don't feel that it makes sense. If you want a dynamic speed, you can already put it in the JointState. -- Sylvain Joyeux (Dr.Ing.) Senior Researcher Space & Security Robotics Underwater Robotics !!! Achtung, neue Telefonnummer!!! Standort Bremen: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 5 28359 Bremen, Germany Phone: +49 (0)421 178-454136 Fax: +49 (0)421 218-454150 E-Mail: [email protected] Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 ----------------------------------------------------------------------- _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
