Skip to content

Commit b92faa9

Browse files
authored
Update README.md
1 parent 80abdac commit b92faa9

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,11 @@ Add as **many** **custom** shadows as you like to any `Xamarin.Forms` view (`And
5353
* Animate any of these property and make the shadows dance around your elements
5454
* No `AndroidX` or `SkiaSharp` dependency required (except Tizen), only `Xamarin.Forms`
5555

56-
## Animate shadows
56+
## Animating shadows
5757

5858
Rendering `Shadows` is cpu intensive (especially on Android).
5959

60-
**Using Xamarin.Forms animation API whith shadows is totally fine**: it won't recreate the Shadows bitmaps.
60+
**Using Xamarin.Forms animation API whith shadows is totally fine**: it won't recreate the `Shadows` bitmaps.
6161

6262
However, animating the color, blur, opacity or size of a `Shade`, will result in creating **multiple bitmap on Android**.
6363

@@ -410,6 +410,8 @@ It will remove some xaml elements:
410410

411411
## Performance
412412

413+
**Warning**: be sure to have the latest version of `Shadows` installed. Very big performance improvements (bitmap caching) have been implement in version 1.2.
414+
413415
* On `Android`, shadows are created thanks to `RenderScript`. Bitmaps are cached in a global `BitmapCache`. For a particular color, size and blur, you will only have one instance alive.
414416
* On `iOS`, a `Shade` is implemented with a simple `CALayer`
415417
* On `UWP`, `Shade` is implemented with `SpriteVisual` drop shadows.

0 commit comments

Comments
 (0)