On Wed, Jul 25, 2012 at 9:27 PM, Peter Soetens <
peter [dot] soetens [..] ...> wrote:

> I believe you're refering to the update hook being called multiple times.
> I have an updatehook redux branch on my github account, but it's still not
> working (hence debug code still being present). The problem is that we need
> some kind of way to distinguish between user triggers and internal
> triggers. Its a quite radical change in the internals of the execution
> engine. There's also the involvement of running update hook after a start()
> or not, and supporting both behaviors...( for example to allow to call
> trigger() in start hook)
>
> Yeah, I think I could have been clearer on which type of service I'm
talking about. In this case, it's an operation, and I'm calling it from
another component through an RTT::OperationCaller<>.

You can see the code here, for clarification:
https://bitbucket.org/jbohren/rtt_geometry/src/b348398ed571/rtt_tf/rtt_t...

Do you think this is still the same behavior as you described above?

-j

Op 25 jul. 2012 15:27 schreef "Jonathan Bohren" <jonathan [dot] bohren [..] ...>
het volgende:

>
> While trying to debug an rtt service I'm working on, I put some debug
statements in the services. When I went to the orocos logfile, I found that
they were being printed out four times per call, and that the member
function was getting invoked four times per call. Is this a bug in rtt, or
am I missing something?
>
> I'm on the toolchain-2.5 tag out of gitorious.

Hi Jonathan,

I believe you're refering to the update hook being called multiple times. I
have an updatehook redux branch on my github account, but it's still not
working (hence debug code still being present). The problem is that we need
some kind of way to distinguish between user triggers and internal
triggers. Its a quite radical change in the internals of the execution
engine. There's also the involvement of running update hook after a start()
or not, and supporting both behaviors...( for example to allow to call
trigger() in start hook)

Any contribution to fix this is welcome but it requires quite some insight
in how activities, the EE and TaskCore work together.

Peter

>
> thanks,
> -j
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>