Question about printing data in the TaskBrowser

Submitted by peter on Thu, 2011-01-27 14:04

I was wondering what would be the most desired way of printing data types in
the taskbrowser. As it is now, if the data has members, these are printed,
otherwise the data itself is streamed by its operator<<.

I think that KDL types offer an operator<< but also getMember to show the
contents. What would you prefer that the taskbrowser uses operator<< or
getMember() ? Should the taskbrowser always use operator<< when it's available
for that type ?

Peter

‹ Property: ERROR when reading in long value crashes and logger ›
»

Question about printing data in the TaskBrowser

Submitted by snrkiwi on Thu, 2011-01-27 14:04.

On Jan 27, 2011, at 09:00 , Peter Soetens wrote:

> I was wondering what would be the most desired way of printing data types in
> the taskbrowser. As it is now, if the data has members, these are printed,
> otherwise the data itself is streamed by its operator<<.
>
> I think that KDL types offer an operator<< but also getMember to show the
> contents. What would you prefer that the taskbrowser uses operator<< or
> getMember() ? Should the taskbrowser always use operator<< when it's available
> for that type ?

For a compound type, shouldn't it be up to the type to display itself logically. Rather than each sub-(sub-)-member. So I recommend sticking with operator<<
S

»