- 03 11月, 2014 8 次提交
- 31 10月, 2014 1 次提交
-
-
由 Sam Judd 提交于
Fixes #225.
-
- 30 10月, 2014 2 次提交
- 29 10月, 2014 2 次提交
- 28 10月, 2014 1 次提交
-
-
由 Sam Judd 提交于
Hack for #219
-
- 27 10月, 2014 7 次提交
-
-
由 Sam Judd 提交于
Fixes #171.
-
由 Sam Judd 提交于
Fixes #217.
-
由 Sam Judd 提交于
Fixes #216.
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
This does not make GifDecoder thread safe in that it doesn't guarantee that a decoder will decode a particular frame, but should keep state consistent and prevent crashes from concurrent writes to buffers. Fixes #212.
-
由 Sam Judd 提交于
Progress toward #212.
-
- 24 10月, 2014 7 次提交
- 23 10月, 2014 7 次提交
- 22 10月, 2014 2 次提交
- 21 10月, 2014 3 次提交
-
-
由 Sam Judd 提交于
Each time we call get() on a drawable resource, we get a new Drawable. We call get() repeatedly on resources when they are retrieved from either the set of active resources or the in memory cache. Each time we create a new GifDrawable it holds on to one or two temporary Bitmaps outside it's shared state to render the current frame and obey the dispose_previous method. This change means we more aggressively cleanup those resources when we think each Drawable is no longer being used. The side affect is that we may reset back to the beginning of the Drawable in some circumstances. Cleanup in in memory resources makes it less likely that frames would be retrieved from in memory, so this also works toward #207.
-
由 Sam Judd 提交于
Fixes #207.
-
由 Sam Judd 提交于
-