[prev in list] [next in list] [prev in thread] [next in thread] 

List:       orocos-dev
Subject:    [Orocos-Dev] [Bug 623] DataPort and BufferPort do not cause to emit events when added as EventPort.
From:       peter.soetens () fmtc ! be (Peter Soetens)
Date:       2009-02-26 12:07:26
Message-ID: E1Lcf1S-0003Dc-D8 () www ! fmtc ! be
[Download RAW message or body]

For more infomation about this bug, visit <https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=623>




--- Comment #2 from Peter Soetens <peter.soetens at fmtc.be>  2009-02-26 13:07:26 ---
Another note concerning event based data ports:

Doing multiple start/stop cycles will cause your component to be woken up two,
three,... times for each event port, because the registration is re-done
(accumulates) upon each start(). I'll fix this for 1.8.1 by only registering
during the first start() and add this note to the manual:

"In the current implementation, addEventPort() must happen before you 
start() the TaskContext the first time.
Any ports added after your component has been started 
the first time will not cause them to wake up your component. 
So even stopping and starting wil not solve this. Therefor,
it is recommended to only use addEventPort in your component's 
contructor. This issue is being looked at."

The event registration should have happened during configure() and
not during start() in my opinion. This would imply that after addEventPort()
has been used, configure() is mandatory OR that addEventPort does the
event connection setup right away for the TaskContext. Which is probably
the most desirable solution.

-- 
Configure bugmail: https://www.fmtc.be/bugzilla/orocos/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.

[prev in list] [next in list] [prev in thread] [next in thread]