[TIMOB-4545] Android: Some ScrollView Scroll Event properties not supported
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Won't Do |
Resolution Date | 2020-01-09T19:16:48.000+0000 |
Affected Version/s | Release 1.7.1 |
Fix Version/s | n/a |
Components | Android |
Labels | parity |
Reporter | Miguel Vizcaino |
Assignee | Unknown |
Created | 2011-07-04T12:08:48.000+0000 |
Updated | 2020-01-09T19:16:48.000+0000 |
Description
Accordingly to the Ti SDK 1.7.1 documentation:
The "scroll" event of a ScrollView should return some properties.
h5.* decelerating
h5.* dragging
h5.* globalPoint
h5.* x, y
{quote}
- Only *x* & *y* properties work fine on both platforms .
- *decelerating* and *dragging* don't work on Android. They are always been returned as _NULL_
- *globalPoint* is never displayed on +iOS or Android+
{quote}
var w = Ti.UI.createWindow({
backgroundColor: 'white'
});
var v = Ti.UI.createView({
backgroundColor:'blue',
borderRadius:10,
width:300,
height:2000,
top:10
});
var s = Ti.UI.createScrollView({
contentHeight: 1000,
showVerticalScrollIndicator:true,
scrollType: "vertical",
});
s.addEventListener('scroll', function(e){
alert("decelerating: " + e.decelerating);
alert("dragging: " + e.dragging);
alert("(x, y): 2 + e.x + ", " + e.y);
alert("globalPoint: "+ e.globalPoint.x +", "+ e.globalPoint.y);
});
s.add(v);
w.add(s);
w.open();
globalpoint is being deprecated. Ticket timob-5118.
Splitting this into an APIDoc bug and a parity bug. Reassigning to Opie for consideration--hope that's OK.
Hi guys, dragging & decelerating are still not working for Android. Dragging returns undefined; TiSDK 7.4.1GA. Please look at it, thanks...
It has been decided that this issue should be closed as “Won’t do.” This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. Updating, or creating code may not reproduce the issue reported, or be a valid test case. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.