[TIMOB-20476] Android: TableView content hidden on rows that are not screen visible (android)
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Not Our Bug |
Resolution Date | 2019-10-14T21:00:39.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | alloy, android, engTriage, rotate, tableView, widget |
Reporter | Ricardo Pereira |
Assignee | Gary Mathews |
Created | 2016-02-18T10:29:15.000+0000 |
Updated | 2019-10-14T21:00:39.000+0000 |
Description
I've a calendar widget, that is a TableView rotated -90 degrees, after set the TableView data, I add a View rotated 90 degrees the TableViewRows, and set to those Views the new height and width.
On 'scrollend' event, if this reach the TableView limits, at the end of the TableView I push another 20 rows to the end of the TableView data, and at the beginning I unshift 20 rows to the beginning of the TableView data.
This works perfectly on iOS, but on android there is a issue that I can't understand why: all the screen visible TableViewRows are fine (5), but when I scroll to the other TableViewRows it's children are hidden until a 'click' event on the TableView.
* Start of the TableView (with 20 rows):
!http://i.stack.imgur.com/ad83i.png!
* Scrolled a little bit to see the next rows (starting on nÂș6):
!http://i.stack.imgur.com/wucDQ.png!
* After a click on TableView:
!http://i.stack.imgur.com/PXkrk.png!
Stackoverflow: [https://stackoverflow.com/questions/35433035/tableview-content-hidden-on-rows-that-are-not-screen-visible-android](https://stackoverflow.com/questions/35433035/tableview-content-hidden-on-rows-that-are-not-screen-visible-android)
Test project added (without assets)
Attachments
File | Date | Size |
---|---|---|
test.cal.zip | 2016-02-18T10:28:33.000+0000 | 651116 |
Hello [~gmathews] - could you take a look? We've been unable to determine root cause. We'd like another set of eyes on this one. If possible to do, we can put it in a sprint. Didn't want to leave it constantly moving to the next sprint.
The issue here is in the third-party
calendar
widget, that we do not own or maintain. Like Alan, I can't get thecalendar
widget to function correctly. Closing as invalid.