Posts: 17,859
Joined: Jul 2011
Reputation:
371
2013-08-21, 21:10
(This post was last modified: 2013-08-21, 21:19 by Martijn.)
This thread is to collect sections where Dirty Regions (DR) fails to properly do it's job and further discuss improvements.
Note:
not all posted finding will be bugs. They may well be how is supposed to be
Below post i will add the DR mode option used for clarity
Posts: 75
Joined: Aug 2013
Reputation:
2
one frame defects can be considered as acceptable, as they doesn't cause user inconveniences. please, only ones with permanent CPU usage.
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
Confirming Martijn's observation in post #2: within Settings, selecting an option on the right side of the screen leaves the Section heading/label in the left hand column permanently "dirty".
On a Raspberry Pi (with all of stupid-boys recent GUI patches), this means the difference between 25% CPU load (dirty regions working correctly) and 65% CPU load (single item permanently - and incorrectly - dirty).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 75
Joined: Aug 2013
Reputation:
2
MilhouseVH, reason for #2 is in #9. i can't fix this as it is 'by design'. sorry for that.
Posts: 75
Joined: Aug 2013
Reputation:
2
ok, it is clear you didn't looked at code. will explain in short.
this function changes alpha and sets this button focused in order to use its focused image. that SetFocus invalidates its region. after Process it restores button to unfocused, again invalidating it, but this time without result. trick used here is focused image + some alpha to made that glory.
..... and debugging this you will end with 2 focused controls at the same time, don't ask me how stupid i was looking at debugger at this moment ....