SMTK
@SMTK_VERSION@
Simulation Modeling Tool Kit
|
Delete components from a resource. More...
#include <Delete.h>
Public Member Functions | |
smtkTypeMacro (smtk::markup::Delete) | |
smtkSharedFromThisMacro (smtk::operation::Operation) | |
smtkSuperclassMacro (smtk::graph::Delete) | |
smtkCreateMacro (smtk::operation::Operation) | |
bool | ableToOperate () override |
void | setSuppressOutput (bool suppress) |
Set/get whether log messages should be suppressed. More... | |
bool | suppressOutput () const |
Protected Member Functions | |
Delete::Result | operateInternal () override |
const char * | xmlDescription () const override |
Protected Attributes | |
Result | m_result |
bool | m_suppressOutput { false } |
Delete components from a resource.
This operation subclasses the abstract smtk::graph::Delete and – if you subclass the markup resource – you must subclass this operation as well, overriding operationInternal() and ableToOperate() in order to pass helper methods your resource's Traits object.
Given a set, S, of nodes to remove, this operation will examine graph arcs connected to all members of S and, if any are marked with OwnershipSemantics, either: (a) insert dependent nodes into S so that they are also removed or (b) refuse to operate in order to preserve semantic consistency. Which of these is done depends on whether the "delete dependents" parameter is enabled or not.
Assuming semantic consistency allows the operation to proceed,
|
inline |
Set/get whether log messages should be suppressed.
Ephemeral cells created by primitive selections use this to prevent confusing the user when the selection is deleted. You should not normally need to use this feature.