Hi,
In fact this behavior comes from the UML specification itself (UML 2.5 section 13.3.4) which is, for me, logical.
An SignalEvent represents the occurences of a given Signal.
So two SignalEvent related to the same Signal does not make sense, because they both represents occurences of the same Signal. So it is logical to not be able to distinguish them because they are the same concepts...
Hoping it helps,
EBR
In fact this behavior comes from the UML specification itself (UML 2.5 section 13.3.4) which is, for me, logical.
An SignalEvent represents the occurences of a given Signal.
So two SignalEvent related to the same Signal does not make sense, because they both represents occurences of the same Signal. So it is logical to not be able to distinguish them because they are the same concepts...
Hoping it helps,
EBR