DslDefinitionModelDeleteClosure Class

Reference

Definition

Namespace:: Microsoft.VisualStudio.Modeling.DslDefinition

Assembly:: Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.15.0.dll

Important

Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Remove closure visitor filter

public ref class DslDefinitionModelDeleteClosure : Microsoft::VisualStudio::Modeling::DslDefinition::DslDefinitionModelDeleteClosureBase, Microsoft::VisualStudio::Modeling::IElementVisitorFilter

[System.CLSCompliant(true)]
public class DslDefinitionModelDeleteClosure : Microsoft.VisualStudio.Modeling.DslDefinition.DslDefinitionModelDeleteClosureBase, Microsoft.VisualStudio.Modeling.IElementVisitorFilter

[<System.CLSCompliant(true)>]
type DslDefinitionModelDeleteClosure = class
    inherit DslDefinitionModelDeleteClosureBase
    interface IElementVisitorFilter

Public Class DslDefinitionModelDeleteClosure
Inherits DslDefinitionModelDeleteClosureBase
Implements IElementVisitorFilter

Inheritance: Object

DslDefinitionModelDeleteClosureBase
DslDefinitionModelDeleteClosure

Attributes: CLSCompliantAttribute

Implements: IElementVisitorFilter

Remarks

Class is defined in ..\GeneratedCode\DomainModel.cs, which is generated from the DSL Definition model.

Constructors

DslDefinitionModelDeleteClosure()

Constructor

Methods

ShouldVisitRelationship(ElementWalker, ModelElement, DomainRoleInfo, DomainRelationshipInfo, ElementLink)

Called to ask the filter if a particular relationship from a source element should be included in the traversal

(Inherited from DslDefinitionModelDeleteClosureBase)

ShouldVisitRolePlayer(ElementWalker, ModelElement, ElementLink, DomainRoleInfo, ModelElement)

This method is called to ask the filter if a particular role player associated with an ElementLink should be Visited during traversal. This overrides the generated ShouldVisitRolePlayer() method, which examines the PropagateDelete attribute on the ElementLink to decide whether to visit the associated role players. In this case the RelationshipPort, the shape drawn as a little square where a relationship is connected to a class, was not deleted with the relationship. The reason is that the link used to connect the RelationshipPort (a shape) to the RoleConnector (also a shape) is a subtype of ElementLink called LinkConnectsToNode. Instances of this link type are used to associate various NodeShapes with LinkShapes and so do not propagate deletes, although in the case of the RelationshipPort it should. The same problem existed for InheritancePort, which like RelationshipPort extends TogglePort.

This method is called for every ElementLink visited during a delete. If the link in question is an instance of LinkConnectsToNode and the roleplayer is a TogglePort, then the port shape may not be needed anymore. By checking how many links are left to the target role player this method returns VisitorFilterResult.YES if there is exactly one link to the port, VisitorFilterResult.DoNotCare otherwise. This ensures that when the last link to the node is deleted the port shape is deleted as well.

Applies to

Partilhar via