Lifecycle & Capabilities

TonCut Desktop treats plugins as long-lived integrations discovered at startup. The host loads every .plg, calls TcpInitializeV2, checks EngineVersion, applies UiScale, and then keeps the resulting ITcPlugin instance alive for extension matching and user-triggered actions.

Lifecycle

The Desktop host behavior inferred from the published wrapper is:

1. Scan Plugins\ recursively for .plg files.
2. Load the binary and resolve TcpInitializeV2.
3. Call Initialize(aRegRoot, aLanguageId, aTonCut) and keep the returned object.
4. Compare EngineVersion with the current Desktop engine version shown in the header badge.
5. Push UiScale and current language into the plugin when state changes.
6. Call LoadConfig while loading plugin settings and SaveConfig before shutdown.
7. Call Finalize before releasing the plugin instance.

Use Configure and About only when the matching

function TCsvImportExportPlugin.GetEngineVersion(): Integer;
begin
  Result := cEngineVersion;
end;

procedure TCsvImportExportPlugin.SetLanguageId(aLanguageId: Integer);
begin
  FLanguageId := aLanguageId;
end;

procedure TCsvImportExportPlugin.SetUiScale(aScale: Single);
begin
  FUiScale := aScale;
end;

These lifecycle members stay in native code for the split C# starter. The managed CSV library has no direct ITcPlugin state or engine-version contract.

Capability flags

If a feature is absent, the matching callback should return

function TCsvImportExportPlugin.GetFeatures(): TTcpFeatures;
begin
  Result := [feImport, feExport];
end;

The C# starter's native shim advertises features. The managed CSV library does not publish TTcpFeatures or a direct plugin interface.

Result codes

function TCsvImportExportPlugin.IsMyFile(const aFileName: WideString): TTcpResult;
begin
  Result := ValidateHeader(aFileName);
end;

The native shim maps headerIsValid to the host's