@@ -32,7 +32,7 @@ It depends on your targetAPI:
32
32
- ` targetAPI == 29 ` , please enable ` requestLegacyExternalStorage ` feature for your project : D
33
33
- ` targetAPI >= 30 ` , don't use this lib. We don't support scope storage for now :(
34
34
- Unless Google release new external permission or other new feature, we would not consider support scope storage. (or says: "I can't do this")
35
- - Or, ofcouse , you are welcome for give us some ideas. Just create a new issues.
35
+ - Or, of course , you are welcomed for give us some ideas. Just create a new issues.
36
36
37
37
## Download
38
38
@@ -70,24 +70,14 @@ The library requires one permissions:
70
70
71
71
If you do not have permission to apply, this framework will check and apply at startup.
72
72
73
- ### Launch 🚀 (Kotlin)
73
+ ### Launch 🚀
74
74
75
- ``` java
75
+ ``` kotlin
76
76
FilePickerManager
77
- .from(this @SampleActivity )
77
+ .from(context )
78
78
.forResult(FilePickerManager .REQUEST_CODE )
79
79
```
80
80
81
- Now that you have taken off 🛩️ ... ( there are really only two lines )
82
-
83
- You only need to add ` .INSTANCE ` to use it:
84
-
85
- ``` java
86
- FilePickerManager . INSTANCE
87
- .from(this )
88
- .forResult(FilePickerManager . REQUEST_CODE );
89
- ```
90
-
91
81
92
82
93
83
### Receive Result
@@ -111,21 +101,6 @@ override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?)
111
101
112
102
The result is a path list of the selected file (` ArrayList<String>() ` ).
113
103
114
- ## proguard-rules(For pre v0.5.1)
115
-
116
- ``` pro
117
- -keepnames class kotlinx.coroutines.internal.MainDispatcherFactory {}
118
- -keepnames class kotlinx.coroutines.CoroutineExceptionHandler {}
119
- -keepnames class kotlinx.coroutines.android.AndroidExceptionPreHandler {}
120
- -keepnames class kotlinx.coroutines.android.AndroidDispatcherFactory {}
121
-
122
- -keepclassmembernames class kotlinx.** {
123
- volatile <fields>;
124
- }
125
-
126
- ```
127
-
128
- Starting with 0.5.2, we removed the coroutine library and implemented it using native threads, so there is no need to add proguard-rules.
129
104
130
105
## Docs
131
106
0 commit comments