Three components are provided that enable applications to support Windows Explorer file drag and drop. The components are:

• TPJDropFiles - This windowed component catches files dropped anywhere over its window. It can act as a container for other components.
• TPJFormDropFiles - This non-visual component catches files dropped anywhere on its form, including the non-client areas.
• TPJCtrlDropFiles - This non-visual component catches files dropped on an associated TWinControl or TFrame.

Key features of these components are:

• An OnDropFiles event is triggered when files are dropped.
• The names of dropped files are made available through the Files array property. For convenience, the name of the first file is also stored in the FileName property.
• The list of dropped files can be configured to include only files, only folders or all files and folders.
• Dropped folders can be recursed so that all the files and sub-folders in each of the dropped folders are listed.
• Filters can be applied to the dropped files and folders. This is done in one of two ways: (1) by handling the OnFileFilter event and deciding which files and folders to pass through the filter and (2) by linking the drop file component to a special file filter component, derived from the abstract TPJFileFilter. In this case the dropped files are automatically filtered by the filter component. Two filter components are provided: TPJExtFileFilter that filters according to file extensions and TPJWildCardFileFilter that filters using DOS-style wildcards. Developers can create further filter components by deriving from TPJFileFilter.
• The mouse co-ordinates where the files were dropped can be retrieved, as can a reference to any control under the mouse cursor at the time.
• The OnBeforeDrop event can be used to do pre-processing before the files are actually dropped.
• The IsFolder array property tells if an equivalent item in the Files list is a file or a folder.
• The owning window can be brought to the front when files are dropped.
• Some design time assistance is provided by component and property editors.

A Delphi 3-7 OpenHelp compatible help file is supplied. Additionally an a-link keyword file is provided for use with Delphi 6/7.

These sources provide a Delphi (2-8 and 2005) direct interface to PGP requiring a preceding (!) full installation of PGP 6.5.x, 7.x, 8.x or 9.x.

Available capabilities:

• Encoding and decoding (encryption/decryption/signing/verifying)
• Creating and verifying file detached (Open)PGP signatures
• Importing, exporting, revoking, deleting keys & certificates
• Several key & certificate management functions
• Key & certificate generation (DH/DSS, RSA)
• x.509 certificate & S/MIME support
• Keyserver functions
• Some utilities

New in Version 4.5.2:

• Signing data without using PGP's passphrase dialog in TPGPEncode shouldn't cause access violations anymore.
• CreateX509CertificateFromRequest in X509Funcs.pas now returns a CertPropsList instead of a CertPropsRec.
• GetKeySetByAnyID in KeyFuncs.pas doesn't try to process non-empty blank IDs (spaces, e.g.) anymore.
• PGP's dialog for certificate selection shouldn't occasionally hide in background anymore.

Main features:

• Building a user interface (UI) out of an XML source at run time. The XML source can be loaded from a file, memory or a resource. The XML source can be loaded as text or in the form of "binary XML" (the more compact "compiled" form).
• Independence from screen resolution. If the screen resolution on the target system differs from the screen resolution on the machine where the XML source was created, XI will scale controls accordingly.
• Easy-to-use data exchange interface for generated UI. By default, registry and INI files are supported.
• Basic set of controls, including the set of controls from JVCL.
• Expandability. You can add your own controls with ease.
• Detailed documentation explaining every aspect of using XI.
• Easy-to-use XML source editor with previewing the resulting user interface.