{ "id": "124314", "key": "TIMOB-16147", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2014-01-01T18:01:26.000+0000", "priority": null, "labels": [], "versions": [ { "id": "14982", "description": "Release 3.2.0", "name": "Release 3.2.0", "archived": false, "released": true, "releaseDate": "2013-12-19" } ], "issuelinks": [], "assignee": null, "updated": "2018-02-28T20:03:59.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "It would be nice if you could add an option to have immediate transition when invoking 'setCurrentPage' on Ti.UI.ScrollableView. It is useful if the views are dynamically preloaded, and helps to allow rotating the views w/o the user noticing it. e.g. scroll a large amount of data, and have only a couple of views initialized\r\nOn IOS it already works this way.\r\nFor Android, i tried to hardcode it in TiUIScrollableView.java, method move(int), line 383, to\r\nmPager.setCurrentItem(index, false); //false = immediate transition\r\nand it works as expected (but is not configurable)", "attachment": [], "flagged": false, "summary": "Android: Support immediate transition for Ti.UI.ScrollableView.setCurrentPage", "creator": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "3.2.0 GA, Android", "comment": { "comments": [ { "id": "286510", "author": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Hi Vladimir,\n\nHave you tried using the currentPage API? If I understood correctly, this is what you're looking for\n{code}\nvar scrollable = Ti.UI.createScrollableView({\n views: [ view1, view2, view3, view4, etc..],\n currentPage: 2\n});\n// or\nscrollable.setCurrentPage(2);\n{code}\nhttp://docs.appcelerator.com/titanium/latest/#!/api/Titanium.UI.ScrollableView-method-setCurrentPage\n\n\n", "updateAuthor": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-01-02T18:47:40.000+0000", "updated": "2014-01-02T18:47:40.000+0000" }, { "id": "286523", "author": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi Pedro,\nYes - this is the API I am using. But on IOS it transitions immeidately to the specified page. While on Android it does a smooth transition. It would be good if this was configurable (Simillar like in the ScrollView - http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.UI.ScrollView-method-setContentOffset)\n\nLike I said - the underlying implementation of ViewPager supports it - it just needs to be called with the specified parameter.\n\nRegards, Vladimir", "updateAuthor": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-02T20:07:19.000+0000", "updated": "2014-01-02T20:07:19.000+0000" }, { "id": "286563", "author": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi Pedro,\n\nNow i saw that i have confused you by giving the wrong method name \"setPosition\" instead of \"setCurrentPage\". Sorry for that. I meant the latter. I fixed the description and short text of the issue to reflect this\n\nRegards, Vladimir", "updateAuthor": { "name": "vlast3k", "key": "vlast3k", "displayName": "Vladimir S", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-03T04:31:43.000+0000", "updated": "2014-01-03T04:31:43.000+0000" }, { "id": "287168", "author": { "name": "ragrawal", "key": "ragrawal", "displayName": "Ritu Agrawal", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Moving this enhancement request to engineering for further evaluation and prioritization. ", "updateAuthor": { "name": "ragrawal", "key": "ragrawal", "displayName": "Ritu Agrawal", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-08T06:28:43.000+0000", "updated": "2014-01-08T06:28:43.000+0000" }, { "id": "398581", "author": { "name": "topener", "key": "topener", "displayName": "Rene Pot", "active": true, "timeZone": "Europe/Berlin" }, "body": "I guess this ticket can be closed as the functionality is here already?", "updateAuthor": { "name": "topener", "key": "topener", "displayName": "Rene Pot", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-10-11T09:59:53.000+0000", "updated": "2016-10-11T09:59:53.000+0000" } ], "maxResults": 5, "total": 5, "startAt": 0 } } }