Enhancement #946
Make causes semantically identifiable
Status: | New | Start date: | 03/13/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | rsb-1.0 |
Description
The current cause vector it is quite hard to use in components because there is no chance to find a certain causing EventId from a semantic name.
Imagine e,g. the case that a component receives an event with two causes (image and sound for instance) and this component needs to look up the respective image cause event in a buffer. Right now there is no chance except iterating over all causes and asking the buffer whether it knows the EventId.
A simple solution would be to add a string tag for each cause. However, I do not know if this is a smart idea or if it is too general. For example, clients then need to know specific string tags. Maybe at least a pre-sorting by the scope of the causing event would be good?
History
#1 Updated by S. Wrede almost 12 years ago
- Target version changed from rsb-0.7 to rsb-0.9
#2 Updated by J. Moringen over 11 years ago
- Target version changed from rsb-0.9 to rsb-0.10
#3 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#4 Updated by J. Moringen about 10 years ago
- Target version changed from rsb-0.11 to rsb-0.12
#5 Updated by J. Moringen about 9 years ago
- Target version changed from rsb-0.12 to rsb-1.0