iText 7 7.1.8 API
|
This class shall be used for creation of destinations, associated with outline items, annotations or actions within current document. More...
Public Member Functions |
|
PdfExplicitDestination (PdfArray pdfObject) | |
override PdfObject | GetDestinationPage (IDictionary< String, PdfObject > names) |
Public Member Functions inherited from iText.Kernel.Pdf.PdfObjectWrapper< PdfObject > | |
virtual T | GetPdfObject () |
virtual iText.Kernel.Pdf.PdfObjectWrapper< T > | MakeIndirect (PdfDocument document, PdfIndirectReference reference) |
Marks object behind wrapper to be saved as indirect. More... |
|
virtual iText.Kernel.Pdf.PdfObjectWrapper< T > | MakeIndirect (PdfDocument document) |
Marks object behind wrapper to be saved as indirect. More... |
|
virtual iText.Kernel.Pdf.PdfObjectWrapper< T > | SetModified () |
virtual void | Flush () |
virtual bool | IsFlushed () |
This class shall be used for creation of destinations, associated with outline items, annotations or actions within current document.
This class shall be used for creation of destinations, associated with outline items, annotations or actions within current document. If you need to create a destination, associated with an object in another PDF (e.g. Remote Go-To actions or Embedded Go-To actions), you should use PdfExplicitRemoteGoToDestination class instead. Note that despite methods with integer value for page parameter are deprecated in this class, Adobe Acrobat handles such destinations correctly, but removes them completely from a PDF, when it is saved as an optimized pdf with the "discard-invalid-links" option. Therefore it is strongly recommended to use methods accepting pdfPage instance, if the destination is inside of the current document.