DirTree Delphi ActiveX Reference Documentation

TCkDirTree

Current Version: 10.1.2

API for iterating over the files and sub-directories in a directory tree. The intent of this class is to provide a simplified, non-recursive way to iterate over an entire directory tree.

Importing the Chilkat ActiveX into Delphi

Important: When upgrading to a new version of Chilkat, make sure to re-imported ActiveX DLL into Delphi to regenerate the files described below.

Chilkat v9.5.*: If using Chilkat v9.5.*, then use "Chilkat_v9_5_0_TLB" instead of "Chilkat_TLB", and the DLLs are named ChilkatAx-9.5.0-win32.dll (or ChilkatAx-9.5.0-x64.dll).

Two things are required to use an ActiveX in Delphi:

The ActiveX DLL needs to be registered via regsvr32 on the system where the Delphi application runs. See How To Register ActiveX DLLs for detailed information.
See also: ActiveX Registration Tutorial
The ActiveX component needs to be "imported". Use the Delphi Import Component Wizard to import the Chilkat type library. This creates the following files: Chilkat_TLB.pas and Chilkat_TLB.dcr. The Chilkat_TLB.pas should be added to your project.

To import the Chilkat type library, do the following:

In the Delphi RAD Studio, select the menu item "Component" --> "Import a Type Library".
Find "Chilkat ActiveX" in the list and select it. This will only appear in the list if the ChilkatAx-win32.dll (or ChilkatAx-x64.dll) has been registered w/ regsvr32.
Check the "Generate Component Wrappers" checkbox.
Select a directory where the unit files (.pas and .dcr) should be generated.
Select "Create Unit" and then "Finish".
Add the .pas to your Delphi project.

To use a Chilkat ActiveX object in your Delphi code, add "Chilkat_TLB" to the "uses" statement. For example:

uses
  Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
  Vcl.Controls, Vcl.Forms, Vcl.Dialogs, Vcl.StdCtrls, Chilkat_TLB;

Object Creation

var
obj: TCkDirTree;
...
begin
obj := TCkDirTree.Create(Self);
...
// When finished, free the object instance.
obj.Free();

Properties

BaseDir

property BaseDir: WideString

Begin iterating from this directory.

More Information and Examples

Iterate over Files and Directories in Filesystem Directory Tree

DebugLogFilePath

property DebugLogFilePath: WideString

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

A timeout property set to 0, indicating an infinite timeout.
A hang occurring within an event callback in the application code.
An internal bug in the Chilkat code causing the hang.

More Information and Examples

Example showing how to use DebugLogFilePath.

DoneIterating

property DoneIterating: Integer readonly

Set to 1 when the last file or sub-directory has been iterated.

FileSize32

property FileSize32: Integer readonly

The file size of the current file in the iteration. (0 if it is a directory.)

FileSizeStr

property FileSizeStr: WideString readonly

Introduced in version 9.5.0.88

The file size of the current file in the iteration as a decimal string. (0 if it is a directory.)

FullPath

property FullPath: WideString readonly

The absolute directory path of the current file or sub-directory.

FullUncPath

property FullUncPath: WideString readonly

The absolute UNC directory path of the current file or sub-directory.

IsDirectory

property IsDirectory: Integer readonly

1 if the current position is a sub-directory, 0 if it is a file.

LastBinaryResult

property LastBinaryResult: OleVariant readonly

This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. It is only accessible if Chilkat.Global.KeepBinaryResult is set to 1. This feature allows for the retrieval of large varbinary results in an SQL Server environment, which has restrictions on returning large data via method calls, though temp tables can handle binary properties.

LastErrorHtml

property LastErrorHtml: WideString readonly

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

LastErrorText

property LastErrorText: WideString readonly

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

More Information and Examples

Concept of LastErrorText LastErrorText Standard Information

LastErrorXml

property LastErrorXml: WideString readonly

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

LastMethodSuccess

property LastMethodSuccess: Integer

Indicates the success or failure of the most recent method call: 1 means success, 0 means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages.

LastStringResult

property LastStringResult: WideString readonly

In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.

More Information and Examples

Long Strings Returned by ActiveX Methods in SQL Server

LastStringResultLen

property LastStringResultLen: Integer readonly

The length, in characters, of the string contained in the LastStringResult property.

Recurse

property Recurse: Integer

If 1, the iteration will be recursive. If 0 the iteration is non-recursive. The default value is 1.

RelativePath

property RelativePath: WideString readonly

The relative directory path of the current file or sub-directory. (Relative to the BaseDir)

VerboseLogging

property VerboseLogging: Integer

If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

Version

property Version: WideString readonly

Version of the component/library, such as "10.1.0"

More Information and Examples

How to get the Chilkat version at runtime.

Methods

AdvancePosition

function AdvancePosition(): Integer;

Advances the current position in the directory tree traversal to the next file or sub-directory.

Important: If AdvancePosition returns 0, it can be an error, or it could be that there are no more files and directories. To distinguish between the two cases, examine the DoneIterating property. If DoneIterating is 1, then the 0 return value is not an error, but instead indicates that the end has been reached.

Returns 1 for success, 0 for failure.

More Information and Examples

Iterate over Files and Directories in Filesystem Directory Tree

BeginIterate

function BeginIterate(): Integer;

Begins a directory tree traversal. After calling this method, the various property values such as Fullpath, FileSize32, etc. can be retrieved for the 1st file / sub-directory in the traversal.

Important: If BeginIterate returns 0, it can be an error, or it could be that there are 0 files and directories. To distinguish between the two cases, examine the DoneIterating property. If DoneIterating is 1, then the 0 return value is not an error, but instead indicates 0 files/directories.

Returns 1 for success, 0 for failure.