 | RelationTypes Enumeration |
Represents the relationship between annotations
Namespace:
Patagames.Pdf.Enums
Assemblies:
Patagames.Pdf.Xamarin.iOS (in Patagames.Pdf.Xamarin.iOS.dll) Version: 4.84.2704
Patagames.Pdf (in Patagames.Pdf.dll) Version: 4.84.2704
Syntaxpublic enum RelationTypes
Public Enumeration RelationTypes
public enum class RelationTypes
public enum RelationTypes
Patagames.Pdf.Enums.RelationTypes = function();
Patagames.Pdf.Enums.RelationTypes.createEnum('Patagames.Pdf.Enums.RelationTypes', false);
Members
| Member name | Value | Description |
---|
| NonSpecified | 0 |
The relationship is not specified;
|
| Reply | 1 |
The annotation is considered a reply to the annotation specified by RelationshipAnnotation.
Viewer applications should not display replies to an annotation individually but together in the form of threaded comments;
see remarks section.
|
| Group | 2 |
The annotation is grouped with the annotation specified by RelationshipAnnotation |
Remarks
In PDF 1.6, a set of annotations can be grouped so that they function as a single
unit when a user interacts with them.The group consists of a primary annotation,
which must not have an IRT entry, and one or more subordinate annotations,
which must have an
RelationshipAnnotation property that
refers to the primary annotation and an
Relationship property whose value is Group.
Some entries in the primary annotation are treated as “group attributes” that
should apply to the group as a whole; the corresponding properties in the subordinate annotations should be ignored.
These properties are Contents (or RichText and DefaultStyle),
ModificationDate, Color, Text, Popup, CreationDate, Subject, and IsOpen.
Operations that manipulate any annotation in a group, such as movement, cut, and copy, should be treated by
viewer applications as acting on the entire group.
Note |
---|
primary annotation may have replies that are not subordinate annotation
that is, that do not have an Relationship value of Group |
See Also