> This PR updates the screen for each window even for the case where the old
> screen has been disposed but there is a new screen instance found for such
> window.
>
> This is the case of Android, where the lifecycle of the application allows
> destroying the native screen when the app goes to
On Wed, 4 May 2022 16:03:20 GMT, Jose Pereda wrote:
>> This PR updates the screen for each window even for the case where the old
>> screen has been disposed but there is a new screen instance found for such
>> window.
>>
>> This is the case of Android, where the lifecycle of the application
> This PR updates the screen for each window even for the case where the old
> screen has been disposed but there is a new screen instance found for such
> window.
>
> This is the case of Android, where the lifecycle of the application allows
> destroying the native screen when the app goes to
> When the size of a ListCell is changed and a scrollTo method is invoked
> without having a layout calculation in between, the old (wrong) size is used
> to calculcate the total estimate. This happens e.g. when the size is changed
> in the `updateItem` method.
> This PR will immediately resize