[TIMOB-7040] iOS: Coverflow - navigating away then back to a coverflow results in redraw and sorting issues
GitHub Issue | n/a |
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-02-09T23:52:46.000+0000 |
Affected Version/s | Release 1.8.0.1 |
Fix Version/s | Sprint 2012-01, Release 2.0.0, Release 1.8.1 |
Components | iOS |
Labels | parity |
Reporter | Eduardo Gomez |
Assignee | Vishal Duggal |
Created | 2012-01-09T15:08:36.000+0000 |
Updated | 2012-03-04T21:45:52.000+0000 |
Description
Issue
Images shown in Coverflow has redraw issues if navigating till its end then back from another app tab (As seen in the Kitchen Sink)
Tested on
iPhone 5.0.1
Titanium SDK 1.8.0.1
Steps to reproduce
1.base ui > views> coverflow view> either coverflow local or replace images
2.tap the right arrow until you reach the end of the images
3.tap another tab, wait a second or two
4.tap the base UI tab and check out the screen
results: (screen shot) images are not shown as expected, seems the order is off as well.
Additional data
The picture shows an iPhone 4.3, and an iPhone 5.0.1 on the right
Attachments
Closing this issue Tested with Ti Studio 1.0.8.201201101928 Ti Mob SDK 1.9.0.v20120111233134 OSX Lion iPhone 4S, iPad 2 Expected behavior is shown of cover flow view in KS not having any redraw issue
Thanks Michael, I have the same characteristics, except for the TI Mobile SDK. When will the Ti Mob SDK 1.9.0.v20120111233134 be available for developers?
This fix is already available in 1.9 CI builds.
I tested it downloading the latest CI build and it now works perfectly. Thanks all for your help!
I have noticed another issue in the coverflow. When you give the coverflow view an initial selected index, like this: // create coverflow view with images var cfview = Ti.UI.iOS.createCoverFlowView({ images: images, height: 120, width: 320, backgroundColor:'transparent', selected: 3 }); It would give the same behavior as it did initially in this bug, the images look out of place. Would this be a quick fix? Thanks!
Santiago: Please open another bug for this scenario.
Reopening and closing this issue to update label and Fix Version field.