Summary: Same port names: EventPort in A causes Port in B to
AssignedTo: orocos-dev [..] ...
ReportedBy: steven [dot] bellens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0
I'm not sure whether you guys will consider this as a bug or not, but it's
definitely unexpected behaviour from my side, so I file it here :).
Consider 3 components (A,B,C) which act in an event-driven system:
Component A: wakes up due to an external program, calculates some stuff and
writes the result to its output port 'output_A'
Component B: has an event input port which gets triggered by 'output_A',
calculates some stuff and writes the result to its output port 'output_B'
Component C: has an event input port which gets triggered by 'output_B',
calculates some stuff and writes out.
_BUT_, C, also needs 'output_A' to do its calculations. However it should _not_
be triggered by that port. So both B and C are connected to 'output_A', but in
B its an EventPort, and in C its a normal Port.
as both B and C subscribe to 'output_A', it makes sense to give the
(Event)Input ports the same name (in the TaskBrowser). However, this same name
will cause C to wake up by that port as well!