J
J Kallay
The ConnectionsDeleted and ConnectionsAdded events both pass a Connects
collection. However, I haven't identified a single situation in which that
collection contains more than one Connect object, with neither 1D nor 2D
glue. In circumstances where one would expect a single event with multiple
Connect objects, instead multiple ConnectionsAdded/Deleted events are
raised. This not only makes the Connects parameter (as opposed to a single
Connect object) unnecessary, it can be quite inconvenient. Consider, for
example, the case where a user drags a connector, thereby breaking the glue
at both ends. Supposed we are maintaining a logical model using connectors
(such as in a flowchart, org chart, or brainstorming diagram). The Connects
parameter only provides information about one of the two shapes that the
connector connects. The connector itself already has an empty Connects
collection, so that can't be interrogated. The only way to find out that a
logical connection was broken between two shapes is to save information
about the first Connect object, wait for the second ConnectionsDeleted
event, and check whether the same connector is involved.
So, what IS the point of passing a Connects collection to these event
handlers?
collection. However, I haven't identified a single situation in which that
collection contains more than one Connect object, with neither 1D nor 2D
glue. In circumstances where one would expect a single event with multiple
Connect objects, instead multiple ConnectionsAdded/Deleted events are
raised. This not only makes the Connects parameter (as opposed to a single
Connect object) unnecessary, it can be quite inconvenient. Consider, for
example, the case where a user drags a connector, thereby breaking the glue
at both ends. Supposed we are maintaining a logical model using connectors
(such as in a flowchart, org chart, or brainstorming diagram). The Connects
parameter only provides information about one of the two shapes that the
connector connects. The connector itself already has an empty Connects
collection, so that can't be interrogated. The only way to find out that a
logical connection was broken between two shapes is to save information
about the first Connect object, wait for the second ConnectionsDeleted
event, and check whether the same connector is involved.
So, what IS the point of passing a Connects collection to these event
handlers?