For more information about this bug, visit

peter [dot] soetens [..] ... changed:

What |Removed |Added
---------------------------------------------------------------------------
Target Milestone|--- |1.0.4
Resolution| |FIXED
Status|NEW |RESOLVED

------- Comment #3 from peter [dot] soetens [..] ... 2007-03-16 10:57

$ svn diff
Index: tests/event_test.cpp
===================================================================

For more information about this bug, visit
A comment was added:
------- Comment #2 from peter [dot] soetens [..] ... 2007-03-15 16:53

(In reply to comment #1)
>
> I remember previous options in the configtool about this "do not automatically
> start the completionprocessor". Was this because the CompletionProcessor was
> always created (and started unless this flag was set) in previous orocos
> versions?

No, _that_ flag was a sure sign of featuritis. But when we removed the flag, we
forgot to start it always.

For more information about this bug, visit
A comment was added:
------- Comment #1 from klaas [dot] gadeyne [..] ... 2007-03-15 15:59

(In reply to comment #0)
> Applications using the CompletionProcessor class for processing events will
> notice that events are not processed, unless
> CompletionProcessor::Instance()->start()
> is called. This is a not documented step and was not required in older (pre
> 1.0) Orocos releases.
>
> Since the CompletionProcessor is only created when effectively used by the
> application, there is no reason to not automatically start it, once created.

I remember previous options in the configtool about this "do not automatically
start the completionprocessor". Was this because the CompletionProcessor was
always created (and started unless this flag was set) in previous orocos
versions?