Community
Participate
Working Groups
When creating a trigger for a transition trigger on a conjugated port, the unconjugated directions is used to annotate the usable protocol messages. Given that the transition should be triggered on an incoming message, it is confusing to be shown "out" protocol messages in the selection. I would propose that, to make this less confusing, only the protocol message names be displayed, without their direction, which is, infact, unnecessary in this context.
Pull back to 1.0 if we have time.
I guess that this should not only be considered for the trigger creation dialog itself, but also how the protocol message is displayed in the trigger table in the properties view itself. I assume that if it is found to be confusing to see the direction "out" for protocol messages for conjugated ports in the trigger creation dialog, it is probably equally confusing to see the direction "out" in the trigger table itself in the properties view for a transition. I suggest that if the direction prefix is being removed in the trigger creation dialog, that it is also removed in the trigger table in the properties view as well.
(In reply to Peter Cigehn from comment #2) > I guess that this should not only be considered for the trigger creation > dialog itself, but also how the protocol message is displayed in the trigger > table in the properties view itself. I assume that if it is found to be > confusing to see the direction "out" for protocol messages for conjugated > ports in the trigger creation dialog, it is probably equally confusing to > see the direction "out" in the trigger table itself in the properties view > for a transition. > > I suggest that if the direction prefix is being removed in the trigger > creation dialog, that it is also removed in the trigger table in the > properties view as well. +1
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.
