[TIMOB-6526] Android: Change TiUIImageView start and stop methods to no longer create new runnable
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-12-16T00:57:17.000+0000 |
| Affected Version/s | Release 1.8.0 |
| Fix Version/s | Sprint 2011-49, Release 1.8.0.1, Release 2.0.0 |
| Components | Android |
| Labels | n/a |
| Reporter | Opie Cyrus |
| Assignee | Hieu Pham |
| Created | 2011-12-09T07:46:24.000+0000 |
| Updated | 2014-02-04T00:45:49.000+0000 |
Description
TiUIImageView.java has start and stop methods for animation that create a new runnable for invoking their async counter parts (handleStop, handleStart). This should be changed to use the TiMessenger mechanism used in KrollProxy and other places.
Testing steps: There are 2 cases to test for. 1. Refactoring: Since this is a general refactoring, it would affect Base UI -> Views -> ImageViews -> Image Rapid Update/Animated. Test those two tests to make sure nothing is broken. 2. Fixed delay when click on "stop" in Base UI -> Views -> ImageViews -> Animated. There should be a delay when duration is high (500ms) WITHOUT this fix.
Closing bug. Verified using above test on: SDK build: 1.9.0.v20120210130135 Runtime: V8, Rhino Titanium Studio, build: 1.0.8.201201262211 Device: Droid 3 (2.3.4)