View Single Post
Old 06-06-2022, 12:42 AM   #56
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
That was on the home screen on my end, and was fairly easily reproduced by repeatedly showing/dismissing the same menu popup (be that the wifi or battery one, or NickelMenu's).

That sometimes lead to delayed and tiled flashing in roughly four quadrants (of varying heights, IIRC, and possibly refreshed in sequence in counter-clockwise order, I'd say?).

(That it seems to think that it requires an update, and worse, a flash, in largely unrelated parts of the screen at all is already a bug in the collision handling, but, oh, well ^^).
I can do that as well, but, only if I don't let the popup finish painting. If I wait for the popup to finish, it doesn't refresh the rest of the screen I don't see the full screen refresh. And even when I do it to quickly, it takes few taps to get the flash. And I think when it happens, I end up with multiple popups opened.

I don't find that a problem. Isn't this a case where the number of changes to parts of the screen trigger an escalation of the refresh to the full screen? And it is happening when you are doing an unusual action. But, the frequency of the updates might be what is triggering the escalation. It doesn't happen on my other devices, but, I don't have a Libra 2. That has the same type/model of screen. Does it happen there?
davidfor is offline   Reply With Quote