I"m guessing you are using a tableView that’s smaller than the screen and therefore masked. I’ve not tried this but since you have to provide a width and height and a mask file, I would think it might be best to when you detect the orientation change would be to destroy the old table and re build it with a different width/height and mask file. I’ll get Danny to respond since widgets are key in his memory right now.
Currently, the list I am using goes to the bottom of the screen, so I am not using a mask.
Destroying it and just creating it with a new height seems like the solution.
I was hoping I could just change some property in the tableview instead of rebuilding it again. The bottomPadding property seemed promising, because that adjusts the bottom limit the rows can go before bouncing back.
I"m guessing you are using a tableView that’s smaller than the screen and therefore masked. I’ve not tried this but since you have to provide a width and height and a mask file, I would think it might be best to when you detect the orientation change would be to destroy the old table and re build it with a different width/height and mask file. I’ll get Danny to respond since widgets are key in his memory right now.
Currently, the list I am using goes to the bottom of the screen, so I am not using a mask.
Destroying it and just creating it with a new height seems like the solution.
I was hoping I could just change some property in the tableview instead of rebuilding it again. The bottomPadding property seemed promising, because that adjusts the bottom limit the rows can go before bouncing back.