FileConflictCallback 1.5.4 API


public abstract class FileConflictCallback<T extends Object>

Field Summary

Fields
Modifier and Type	Field	Description
`private CoroutineScope`	`uiScope`

Constructor Summary

Constructors
Constructor	Description
`FileConflictCallback(CoroutineScope uiScope)`
`FileConflictCallback()`

Method Summary

Modifier and Type	Method	Description
`final CoroutineScope`	`getUiScope()`
`final Unit`	`setUiScope(CoroutineScope uiScope)`
`Unit`	`onFileConflict(T destinationFile, FileCallback.FileConflictAction action)`	Do not call `super` when you override this function.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - FileConflictCallback
```
FileConflictCallback(CoroutineScope uiScope)
```
  - FileConflictCallback
```
FileConflictCallback()
```
- Method Detail
  - getUiScope
```
 final CoroutineScope getUiScope()
```
  - setUiScope
```
 final Unit setUiScope(CoroutineScope uiScope)
```
  - onFileConflict
```
@UiThread() Unit onFileConflict(T destinationFile, FileCallback.FileConflictAction action)
```
    Do not call super when you override this function.
    The thread that does copy/move/decompress will be suspended until the user gives an answer via FileConflictAction.confirmResolution. You have to give an answer, or the thread will be alive until the app is killed and end up as a zombie thread. If you want to cancel, just pass ConflictResolution.SKIP into FileConflictAction.confirmResolution. If the worker thread is suspended for too long, it may be interrupted by the system.