[TIMOB-951] Android: support touchEnabled
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:54:46.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 |
| Components | Android |
| Labels | android, feature |
| Reporter | Don Thorp |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T02:39:59.000+0000 |
| Updated | 2011-04-17T01:54:46.000+0000 |
Argh, this one's hitting us. Would really appreciate if documentation specified what is/isn't actually implemented yet!
+1 for Brion's suggestion!
(from [d074f62eaf9b76a99f7bf6684dfb8e918f4aad42]) [#951 state:fixed-in-qa][#1931 state:fixed-in-qa][#1934 state:fixed-in-qa][#1937 state:fixed-in-qa][#1939 state:fixed-in-qa][#1940 state:fixed-in-qa] Fixing regression where keying off of presence of 'click' handler broke the expectation that views are touchable by default. Added support for touchEnabled. If touchEnabled is false, click proceeds through all views until one that handles click and is located under the touch point is found. Several of these defects were side-effects attributable to clickability. http://github.com/appcelerator/titanium_mobile/commit/d074f62eaf9b76a99f7bf6684dfb8e918f4aad42"> http://github.com/appcelerator/titanium_mobile/commit/d074f62eaf9b7...
1.4.2.4ce7ff G1 running 1.6, 2.2 simulator