2020-12-20, 01:00
<gui>
<smartredraw>true</smartredraw>
</gui>
is a great feature and can save resources on some low power devices. However, in certain situations artefacts can be left permanently onscreen whichdisctract from the viewing experience and certain elements are not updated on the screen properly. I'm sure the devs are aware of this and it woulb be nice to have it fixed in time for Matrix final.
Not updating properly: Add-ons that use foreground windows with progress bars (Watchedlist is the add-on with the longest dialogue time); the volume circle thingy.
Artefacts left on screen: Mostly error messages in (upper right-hand) pop-ups from core or add-on that are supposed to vanish after a few seconds.
I guess both kinds of errors could have to do with the time an element stays onscreen. If a certain time is exceeded, smartredraw probably considers the element fixed and will not remove it. Maybe this can be solved programmatically by using a (much?) longer time threshold? The 2nd kind of error might be avoided if those pop-ups were issued not only with a time to display onscreen but a refresh screen at the end.
Of course, these are only layman's descriptions and I have no knowledge of programming. These problems exist indepently of the platform used, I experience them both in Windows and CoreELEC. Thanks in advance for looking into it!
<smartredraw>true</smartredraw>
</gui>
is a great feature and can save resources on some low power devices. However, in certain situations artefacts can be left permanently onscreen whichdisctract from the viewing experience and certain elements are not updated on the screen properly. I'm sure the devs are aware of this and it woulb be nice to have it fixed in time for Matrix final.
Not updating properly: Add-ons that use foreground windows with progress bars (Watchedlist is the add-on with the longest dialogue time); the volume circle thingy.
Artefacts left on screen: Mostly error messages in (upper right-hand) pop-ups from core or add-on that are supposed to vanish after a few seconds.
I guess both kinds of errors could have to do with the time an element stays onscreen. If a certain time is exceeded, smartredraw probably considers the element fixed and will not remove it. Maybe this can be solved programmatically by using a (much?) longer time threshold? The 2nd kind of error might be avoided if those pop-ups were issued not only with a time to display onscreen but a refresh screen at the end.
Of course, these are only layman's descriptions and I have no knowledge of programming. These problems exist indepently of the platform used, I experience them both in Windows and CoreELEC. Thanks in advance for looking into it!
