mcFeaturesChangeMadeEnum Enumeration
|
|
Allowed values for the _DMcFeaturesEvents.ChangeMade and_IMcFeaturesEvents.ChangeMade ChangeFlags argument and also for the
IMcBasicFeatures.NotifyContext property values.
Namespace:
MediaCy.IQL.Features
Assembly:
MediaCy.IQL.Features (in MediaCy.IQL.Features.dll) Version: 10.0.6912.0
SyntaxPublic Enumeration mcFeaturesChangeMadeEnum
Members
| Member name | Value | Description |
---|
| mcfcmNoChanges | 0 | no-changes |
| mcfcmAppearanceOnly | 1 | only appearance-related propertychanged. Changes that have this bit set will not result in
McImage.AoiChanged and McImages.AoiChanged events being fired on the
ActiveImage; you will need to handle events directly from the
ThisApplication.ActiveImage.Aoi should you wish to track such changes. |
| mcfcmPropertyChanged | 2 | some significant property was changed |
| mcfcmFeatureAdded | 4 | feature(s) were added |
| mcfcmFeatureRemoved | 8 | feature(s) were removed |
| mcfcmCoordinatesChanged | 16 | coordinates of feature(s) changed |
| mcfcmUserEdit | 256 | set if the change was caused by a usercreating or editing a linked McGraphObj. |
| mcfcmDragging | 512 | set if the change was caused bydragging a linked McGrapahObj or one of its handles. Events with this bit
set will only happen if the McFeatures.FeatureStatusFlags
mcFeatureStatusFlags.mcfsfTrackDragging bit is set. This is usually set
automatically by setting the McFeatures.OptionFlags
mcOptionFlags.mcofDefaultTrackDragging bit, and in fact this is the only way
to cause the feature to track changes during linked McGraphObj creation.
Changes that have this bit set will not result in McImage.AoiChanged and
McImages.AoiChanged events being fired on the ActiveImage; you will need to
handle events directly from the ThisApplication.ActiveImage.Aoi should you wish to track
such changes. |
| mcfcmCreationNotComplete | 1024 | set if the change was caused by alinked McGraphObj for any change caused by the linked McGraphObj while its
creation is not complete. Events with this bit set will only happen if the
McFeatures.FeatureStatusFlags mcFeatureStatusFlags.mcfsfTrackDragging bit is
set. This is usually set automatically by setting the
McFeatures.OptionFlags mcOptionFlags.mcofDefaultTrackDragging bit, and in
fact this is the only way to cause the feature to track changes during
linked McGraphObj creation.
Changes that have this bit set will not result in McImage.AoiChanged and
McImages.AoiChanged events being fired on the ActiveImage; you will need to
handle events directly from the ThisApplication.ActiveImage.Aoi should you wish to track
such changes. |
| mcfcmDraggingOrCreating | 1536 | |
| mcfcmDuplicateEvent | 2048 | set if the change is a secondFeatureAdded event fired upon completion of creation for a feature for which
an FeatureAdded event was fired during dragging because it had the
McFeatures.FeatureStatusFlags mcFeatureStatusFlags.mcfsfTrackDragging bit is
set. FeatureAdded event handlers either need to ignore the first event (the
one with the mcfcmCreationNotComplete bit set) or the second event (the one
with the mcfcmDuplicateEvent) bit set. |
| mcfcmNoDisplayLimitHit | 4096 | the features count exceeded theFeatures/Limits/NoDisplayFeaturesCount Setting or the value set by assigning
mcsfmmGetOrSetNoDisplayLimit to the SetFromMaskMethod property. When the
event is fired, the PropertyID argument will hold the feature count setting
that was exceeded and the FeatureID arguement gives the current number of
features. This event will preceed other event(s) which describe what changes
were made that lead to the excessive count. |
| mcfcmInBackupRestore | 8192 | The notify is happening due to a McUndoStack.Undoor Redo operation. |
See Also