[TIMOB-1494] Slider Bug in SDK 1.4 on (at least) Android
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:56:19.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 |
| Components | Android |
| Labels | android, defect, slider |
| Reporter | vit |
| Assignee | Don Thorp |
| Created | 2011-04-15T02:54:16.000+0000 |
| Updated | 2011-04-17T01:56:19.000+0000 |
Description
Setting max has no effect in certain situations.
Here is the demo code:
http://pastie.org/1079331">http://pastie.org/1079331 (or see attachment)
Note, that the thumb should be in the middle of the ruler after the code has executed, but ends up closer to the beginning of the ruler, as if max wasn't changed.
Attachments
| File | Date | Size |
|---|---|---|
| app.js | 2011-04-15T02:54:17.000+0000 | 264 |
Verified that we're not recalculating the slider onPropertyChange.
(from [ccf6dce1a4b08b4334df6dd8d261b1aa125ce48e]) [#1494 state:fixed-in-qa] added support for dynamically changing min,max for slider. Added additional KS example and turned slider.js into a launcher. slider.js is now slider_basic.js http://github.com/appcelerator/titanium_mobile/commit/ccf6dce1a4b08b4334df6dd8d261b1aa125ce48e"> http://github.com/appcelerator/titanium_mobile/commit/ccf6dce1a4b08...
confirmed on android and iOS