CanFileBeDeleted Event
Fires when the driver needs to know whether a file or directory can be deleted.
Syntax
// CBFSCanFileBeDeletedEventArgs carries the CBFS CanFileBeDeleted event's parameters. type CBFSCanFileBeDeletedEventArgs struct {...} func (args *CBFSCanFileBeDeletedEventArgs) FileName() string func (args *CBFSCanFileBeDeletedEventArgs) HandleInfo() int64 func (args *CBFSCanFileBeDeletedEventArgs) FileContext() int64 func (args *CBFSCanFileBeDeletedEventArgs) SetFileContext(value int64) func (args *CBFSCanFileBeDeletedEventArgs) HandleContext() int64 func (args *CBFSCanFileBeDeletedEventArgs) SetHandleContext(value int64) func (args *CBFSCanFileBeDeletedEventArgs) CanBeDeleted() bool func (args *CBFSCanFileBeDeletedEventArgs) SetCanBeDeleted(value bool) func (args *CBFSCanFileBeDeletedEventArgs) ResultCode() int32 func (args *CBFSCanFileBeDeletedEventArgs) SetResultCode(value int32) // CBFSCanFileBeDeletedEvent defines the signature of the CBFS CanFileBeDeleted event's handler function. type CBFSCanFileBeDeletedEvent func(sender *CBFS, args *CBFSCanFileBeDeletedEventArgs) func (obj *CBFS) GetOnCanFileBeDeletedHandler() CBFSCanFileBeDeletedEvent func (obj *CBFS) SetOnCanFileBeDeletedHandler(handlerFunc CBFSCanFileBeDeletedEvent)
Remarks
This event fires when the driver needs to know whether the file or directory specified by FileName can be deleted.
To handle this event properly, applications must set the CanBeDeleted parameter appropriately. Please note that the firing of this event does not necessarily mean the specified file or directory will be deleted if CanBeDeleted is set to true, just that the OS needs to know whether it can be deleted.
The HandleInfo parameter carries a handle to an object with information about the file handle. While within the event handler, it can be used to call any of the following methods: GetHandleCreatorProcessId, GetHandleCreatorProcessName, GetHandleCreatorThreadId, or GetHandleCreatorToken.
The FileContext and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, respectively. Please refer to the Contexts topic for more information.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.