| ILockedContent Interface |
Represents a collection of markup data items that has
been locked in order to indicate that they should not be changed
during localization.
Namespace: Sdl.FileTypeSupport.Framework.BilingualApi
Assembly: Sdl.FileTypeSupport.Framework.Core (in Sdl.FileTypeSupport.Framework.Core.dll) Version: 1.0.0.0 (1.0.2551.0)
SyntaxThe ILockedContent type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | Content |
Provides access to the items that have been locked.
|
| IndexInParent |
The index of this item in its parent container (if any).
(Inherited from IAbstractMarkupData.) |
| Parent |
When this item is inside a markup data container, this property
provides access to the parent container.
(Inherited from IAbstractMarkupData.) |
| ParentParagraph |
Convenient accessor to the source or target paragraph container that the
item appears in.
(Inherited from IAbstractMarkupData.) |
| Properties |
Information on the lock
|
Methods| Name | Description | |
|---|---|---|
  | AcceptVisitor |
Part of the visitor pattern implementation for markup data.
This method is overridden in each leaf implementation. The implementation
should call the Visit... method on the visitor corresponding to their object
type, passing themselves (i.e. this) as the parameter.
Objects that contain other objects (e.g. implementations of ISegment or
IOtherMarker) should NOT apply the visitor to their content items.
It must be left to the visitor implementation to 'decide' whether the visitor 'wants'
to visit the sub-items of a node.
(Inherited from IAbstractMarkupData.) |
| RemoveFromParent |
Removes this node from its parent container (if any).
(Inherited from IAbstractMarkupData.) |
RemarksThe locked content item was explicitly NOT made a markup data container in order to avoid accidental access to the locked items when iterating over the tree structure. If required, the locked content can be accessed through the Content property, which is a markup data container.
Locked content can be nested, i.e. there can be other locked content items inside the locked container. The outermost locked content properties always take precedence.
See AlsoCommunityComments