_task_map and musers private

Submitted by Simon on Wed, 2011-03-02 17:04

Hi,

I worked with orocos 1.x before and now I have to devellop an application
with orocos 2.x.

I want to build a componnent that can find by it-self all the components
created by a deployer and add them has its peers. With rtt 1.x, it was
possible to play with "TaskContext::musers" and "TaskContext::_task_map" to
do it.

Now, in rtt 2.2 and 2.3, these two members are private so it's not possible
to do it. Worst, there is no accessor for musers. Why these members now need
to be private? or why there is no accessor to musers?

Thanks for reply

‹ Parallel manipulator support in KDL Problem when reading an xml file ›
»

_task_map and musers private

Submitted by peter on Thu, 2011-03-03 20:36.

On Wed, Mar 2, 2011 at 5:59 PM, Simon Pelletier-Thibault
<simon [dot] pelletiert [..] ...> wrote:
> Hi,
>
> I worked with orocos 1.x before and now I have to devellop an application
> with orocos 2.x.
>
> I want to build a componnent that can find by it-self all the components
> created by a deployer and add them has its peers. With rtt 1.x, it was
> possible to play with "TaskContext::musers" and "TaskContext::_task_map" to
> do it.
>
> Now, in rtt 2.2 and 2.3, these two members are private so it's not possible
> to do it. Worst, there is no accessor for musers. Why these members now need
> to be private? or why there is no accessor to musers?
>

That must be a bug, we did not intend to change that afaikt. So making these
protected again seems fine to me.

Peter

»

_task_map and musers private

Submitted by Simon on Fri, 2011-03-04 17:12.

Ok,

I will ask Philippe Hamelin, to give you the patch

Thanks

On Thu, Mar 3, 2011 at 3:33 PM, Peter Soetens <peter [..] ...>wrote:

> On Wed, Mar 2, 2011 at 5:59 PM, Simon Pelletier-Thibault
> <simon [dot] pelletiert [..] ...> wrote:
> > Hi,
> >
> > I worked with orocos 1.x before and now I have to devellop an application
> > with orocos 2.x.
> >
> > I want to build a componnent that can find by it-self all the components
> > created by a deployer and add them has its peers. With rtt 1.x, it was
> > possible to play with "TaskContext::musers" and "TaskContext::_task_map"
> to
> > do it.
> >
> > Now, in rtt 2.2 and 2.3, these two members are private so it's not
> possible
> > to do it. Worst, there is no accessor for musers. Why these members now
> need
> > to be private? or why there is no accessor to musers?
> >
>
> That must be a bug, we did not intend to change that afaikt. So making
> these
> protected again seems fine to me.
>
> Peter
>

»