Solid File System

Virtual file system enigne that can be embedded into your software.

OnFileDelete event/delegate/callback


Pascal    Plain C    C++ (DLL/Lib)    C++ (VCL)    C++ (.NET)    C#    VB.NET    Java 

SolFSStorage     See also    


This event is fired when the storage needs to be deleted.


    TSolFSDeleteFileEvent = procedure( Sender : TObject; const FileName : TSolFSString; var Result : LongInt) of object;

[Plain C]
    typedef Error (__stdcall *SolFSDeleteFileFunc)( LongWord UserData, PWideChar FileName);

[C++ (DLL/Lib)]
    typedef Error (__stdcall *SolFSDeleteFileFunc)( LongWord UserData, PWideChar FileName);

[C++ (VCL)]
    typedef void (__closure *TSolFSDeleteFileEvent)( System::TObject* Sender, const TSolFSString FileName, Error& Result);

[C++ (.NET)]
    public __delegate void SolFSDeleteFileEvent( SolFSStorage* Sender, System::String* FileName, Int32 __gc &Result);

    public void SolFSDeleteFileEvent( SolFS.SolFSStorage Sender, string FileName, ref int Result);

    Sub SolFSDeleteFileEvent( ByVal Sender As SolFS.SolFSStorage, ByVal FileName As String, ByRef Result As Int32);

    void ISolFSFileEvents.onFileDelete(String fileName)


  • Sender - reference to the class that called the delegate/event handler.
  • FileName - the name of the storage as passed to SolFSStorage.Create constructor.
  • Result - out parameter (return value for DLL) where the application places the result of the operation. If you are working with file system, Win32 error code is a good candidate for placing to Result parameter. Otherwise you can use any other error codes, just be sure that 0 means success.
    [Java]See Description for details about error reporting in Java.

  • [Plain C] UserData - application-defined parameter which is specified when creating the storage and passed back to callback function.


The event is fired when the storage file must be deleted from media.

The callback/event handler must be set before the storage is opened.

You need to implement ISolFSFileEvents interface in your code and pass the object, that implements the events, to one of SolFSStorage constructors that accept storageEvents parameter.

ERROR REPORTING: In Java you can't return more than one parameter, so the natural way is to throw an exception. You can throw any exception, and this exception will be passed back to the code, which called one of SolFS functions. So if you use callback mechanism and throw exception from within event handlers, be sure to wrap each call to SolFS methods with try/catch.

See also

Information about callbacks (Operating System edition only)     OnFileCreate    

Back to top