Skip to main content

TvxFileEventType

TvxFileEventType = (fetNone, fetRead, fetWrite, fetAudit, fetError, fetIssue, fetTemp, fetTransport, fetDelete)

Example​

procedure MarkRead(FileCon: TvxFileCon);
begin
  // fetRead is safe because its script and host ordinals are both 1.
  FileCon.FileEvent := fetRead;
end;

Usage​

TvxFileEventType names Velox file lifecycle events, but values after fetWrite are shifted in the current scripting interface and can record the wrong event.

Members​

ValueOrdinalMeaning
fetNone0No event; maps correctly to Velox fetNone.
fetRead1File read; maps correctly to Velox fetRead.
fetWrite2File written; maps correctly to Velox fetWrite.
fetAudit3Intended audited/moved-to-audit; currently reaches Velox fetDownload.
fetError4Intended error event; currently reaches Velox fetAudit.
fetIssue5Intended issue event; currently reaches Velox fetError.
fetTemp6Intended moved-to-temporary state; currently reaches Velox fetIssue.
fetTransport7Intended transporting state; currently reaches Velox fetTemp.
fetDelete8Intended deletion; currently reaches Velox fetTransport.

Behavior and boundaries​

  • Do not assign fetAudit through fetDelete to a Velox file-event property or method in the current version.
  • The Velox fetDownload (ordinal 3) is not nameable by scripts, yet receives script fetAudit. Velox fetDelete (ordinal 9) is not representable by the current script enum.
  • Reading a Velox value after the gap is also unsafe: the ordinal can be mislabeled, and Velox ordinal 9 lies beyond the script declaration's highest value.
  • This is not merely a display difference. File-event values feed audit/log state and can misrepresent what happened to a file.
  • Persist named business events outside this enum boundary and translate with a tested mapping at the Velox edge.

Additional Technical Info​

TvxFileEventType records the current/lifecycle action for a file connection and file log. The product host enum has ten members, but the script importer omits fetDownload between fetWrite and fetAudit.

Current defect: the TvxFileCon.FileEvent runtime helper assigns the script enum directly to the native enum without an ordinal adapter. Only fetNone, fetRead and fetWrite are safely aligned. Every later script member is interpreted as the preceding native member.

External references

Created 2026-07-15