Skip to content

Commit 16ce20b

Browse files
committed
Update readme about the view to choose
1 parent b312686 commit 16ce20b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ Note: From v0.9.0, `WebImage` supports animated image as well! You can use `.ani
121121
- [x] Supports animation control using the SwiftUI Binding
122122
- [x] Supports indicator and transition, powered by SDWebImage and Core Animation
123123
- [x] Supports advanced control like loop count, playback rate, buffer size, runloop mode, etc
124-
- [x] Supports coordinate with native UIKit/AppKit/WatchKit view
124+
- [x] Supports coordinate with native UIKit/AppKit view
125125

126126
```swift
127127
var body: some View {
@@ -164,7 +164,7 @@ Why we have two different View types here, is because of current SwiftUI limit.
164164

165165
If you don't need animated image, prefer to use `WebImage` firstly. Which behaves the seamless as built-in SwiftUI View. If SwiftUI works, it works.
166166

167-
If you need simple animated image, use v0.9.0 above with `WebImage`. Which provide the animated image support.
167+
If you need simple animated image, use v0.9.0 above with `WebImage`. Which provide the basic animated image support. But it does not support progressive animation rendering, playback rate, etc.
168168

169169
If you need powerful animated image, `AnimatedImage` is the one to choose. Remember it supports static image as well, you don't need to check the format, just use as it.
170170

0 commit comments

Comments
 (0)