On Wed, Jan 8, 2014 at 1:31 PM, Matthias Goldhoorn
<matthias [dot] goldhoorn [..] ...> wrote:
> On 08.01.2014 10:57, Matthias Goldhoorn wrote:
>
> The page:
>
> http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20/methods-vs-ope...
>
> seems outdated, specially the section there it is described how to call a
> operation from the C++ side.
> There is no RTT::Method anymore in master.
> I tried to replace the Method with the instance of the method, but this has
> no way to call it so far i see.
>
> Could anyone please let my know howto call a Operation on a TaskContext.
> (either by accessing the RTT::Operation (which i had), or through the
> TaskContext interface.
> I wannt to go this way, because i want to archive a thread-change.
>
> operation a (caller thread) -> operation b (ownThread)
>
> Or is there a more simply way to archive this behavior?
>
> Greetings,
> Matthias
>
>
> As far i figured our this is the right way:
> (but the doc needs still to be updated)
> RTT::OperationCaller< bool(::std::string const & ) > userMethod =
> this->getOperation("something");
> userMethod( value)

Thanks for reporting, I've updated the wiki to say 'OperationCaller'
instead of 'Method'.

The suggested solution is correct.

Peter

On 01/08/2014 01:31 PM, Matthias Goldhoorn wrote:
> On 08.01.2014 10:57, Matthias Goldhoorn wrote:
>> The page:
>>
>> http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20/methods-vs-ope...
>>
>> seems outdated, specially the section there it is described how to call a operation from the C++ side.
>> There is no RTT::Method anymore in master.
>> I tried to replace the Method with the instance of the method, but this has no way to call it so far i see.
>>
>> Could anyone please let my know howto call a Operation on a TaskContext.
>> (either by accessing the RTT::Operation (which i had), or through the TaskContext interface.
>> I wannt to go this way, because i want to archive a thread-change.
>>
>> operation a (caller thread) -> operation b (ownThread)
>>
>> Or is there a more simply way to archive this behavior?
>>
>> Greetings,
>> Matthias
>
> As far i figured our this is the right way:
> (but the doc needs still to be updated)
> RTT::OperationCaller< bool(::std::string const & ) > userMethod = this->getOperation("something");
> userMethod( value)

The page you refer to dates back to the time when 2.0 was just introduced, to explain the differences between 1.X and 2.0 syntax,
the "core" documentation that (AFAIK) gets updated with every release is the Component Builders manual (under toolchain reference manuals), rather than the wiki documentation.
You can find it here:
http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-compo...

>
>
>
>> --
>> Dipl.-Inf. Matthias Goldhoorn
>> Space and Underwater Robotic
>>
>> Universität Bremen
>> FB 3 - Mathematik und Informatik
>> AG Robotik
>> Robert-Hooke-Straße 5
>> 28359 Bremen, Germany
>>
>> Tel.: +49 421 178 45-4193
>> Zentrale: +49 421 178 45-6550
>> Fax: +49 421 178 45-4150
>> E-Mail:matthias [dot] goldhoorn [..] ...
>>
>> Weitere Informationen:http://www.informatik.uni-bremen.de/robotik
>>
>>
>
>
> --
> Dipl.-Inf. Matthias Goldhoorn
> Space and Underwater Robotic
>
> Universität Bremen
> FB 3 - Mathematik und Informatik
> AG Robotik
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Tel.: +49 421 178 45-4193
> Zentrale: +49 421 178 45-6550
> Fax: +49 421 178 45-4150
> E-Mail:matthias [dot] goldhoorn [..] ...
>
> Weitere Informationen:http://www.informatik.uni-bremen.de/robotik
>
>
>