Trapping EA Events on Connectors & stereotypes - S

[Jeff Bartels]

Does anyone have any comments about why some of the EA events that can be trapped can be controlled (i.e. allowed or inhibited) via a Boolean return value, while others cannot (i.e. the required handler is a method with no return value)? I would love to be able to inhibit certain edits to Packages, Elements, and Connectors in my add-in.
More-specifically, I can trap a user attempt to change the stereotype of a Connector and decide to restore the stereotype to a value of my choosing, but the end result in EA is weird - the user-selected stereotype AND my corrected value are BOTH associated with the connector. Can't seem to find a property on the Connector object that I can manipulate to restore the stereotype to the ONE desired value.

Any suggestions?

[qwerty]

Well, it's EA. We would be happy to see things like you mention realized. But only a few of such user requirements made it to Sparx' development finally. I also used RR in the past (and would not like to go back) and I really appreciated the way the consistently implemented escapes. Sigh...

q.