emitting UserAbortEvent instead of GoalReached on stop()

requested by @christophpohl : the behavior of stop() and stopAll() should be similar in that they both emit the same stop event. Here, we use the UserAbortTriggered event. Previously, (why? :D ) the GoalReached event was used in stopAll.

Todo:

• test on ARMAR-6 / manipulation pipeline

requested review from @christophpohl

assigned to @fabian.reister

changed the description

approved this merge request

added 10 commits

• fdfe83d1...ea1af440 - 9 commits from branch master
• 4de3c89a - Merge remote-tracking branch 'origin/master' into fix/emit-on-user-abort-event-on-stop

Compare with previous version

By ARMAR-6 on 2022-05-04T09:42:36 (imported from GitLab)

The user abort event did not show up in the MemoryViewer. Need to investigate this.

added 11 commits

• 4de3c89a...4d690ca6 - 10 commits from branch master
• 80a7a279 - Merge remote-tracking branch 'origin/master' into fix/emit-on-user-abort-event-on-stop

Compare with previous version

added 3 commits

• 9cc7cafc - using armarx::time
• 70cd3ab2 - impl. aron events / conversion
• fe49a3ea - implementing additional events

Compare with previous version

added 2 commits

• f3cd80fb - moving hard coded names to events.h (will be used elsewhere as well...)
• 3bdae14c - conversion fromAron for events in MemorySubscriber

Compare with previous version

added 1 commit

• 3c2eee4a - fixing conversion of aron event

Compare with previous version

added 1 commit

• 72ed9c4a - reduced verbosity of navigator

Compare with previous version

I fixed all known issues. The example component works nicely.

mentioned in commit ee25209a

merged