can you check if you have "render if unfocused" turned on in the interface settings? cause that sounds like exactly the behavior id expect when having it disabled...
Damn... forgot about that one. So logical when you think about it. And yes, when checked it indeed does respond.
now what i said just above changes a bit with the last build, because i just implemented
ascsd 's suggestion of refreshing the screen only when necessary, so it might be a little hit or miss at times if i forgot some stuff. whereas before it always rendered the interface 60 times per second (if you had the "render if unfocused" setting disabled then only when focused, always otherwise), now it does that only after some change in the interface has been detected, that can be mouse events, scrolling, keyboard, animated images, text input, and some more. please let me know if you find any oddities with inputs and interface responsiveness, stuff like that. also glad to know the tweaks i made to images are actually having positive impacts!
So, with "Render if unfocused" checked and the window actually unfocused, as soon as the mouse is over the window, I see the decimal part of the framerate then changing like there's no tomorrow.
Now here's something different, in list view with the window unfocused, render checkbox ticked and the mouse left untouched over the window, framerate keeps changing. But, after switching to grid view, as soon as I leave the mouse untouched over an unfocused window, framerate freezes. If I now switch back to list view and again unfocus the window, it will then also freeze the framerate after leaving the mouse untouched when it's back over the window. But ONLY if I have switched to grid view before in that session. Contrary to this, if the window IS focused, the framerate freezes immediately in list view after the mouse is outside of the window... doesn't need switching to grid view first.
So far I've not been able to have it NOT scroll when unfocused and with the checkbox ticked... so that's a good thing I guess with the new refresh system.
One thing I did notice, scrolling by dragging the scrollbar in grid view is very unresponsive once all images are showing. If I drag the scrollbar from top to bottom or the other way around, if I do that fast enough I can get it to only redraw 3 or 4 times before I reach bottom or top, framerate then also drops more than 50% at times. The slower I drag the scrollbar, the more responsive it gets. However, using the scroll wheel I also see framerate drop, but not nearly as much and scrolling remains fluid (smooth scroll disabled)
With smooth scroll enabled, using the mouse wheel in grid view behaves 'strange'. It just scrolls as expected for most part of the way from top to bottom or vice versa, but along the way it will stutter a bit at any given point during a continuous scrolling operation regardless of smoothness value (tried 1 to 10), and sometimes it even jumps back a bit before I've reached the bottom or top. With higher smoothness setting (e.g. 10 instead of 1), it is worse no matter where you start scrolling and how far, with a setting of 1 it happens much less but still happens. In list view it behaves like expected, even when giving the mouse wheel a jolt it keeps scrolling smoothly. BTW, this has nothing to do with the way you handle screen refreshing as this also happened before you changed this, I am not a big fan of smooth scroll because it makes precise scrolling tedious to impossible, so have it disabled by default, just tried it to see if that caused other issues and thought to mention it anyway.
Also noticed that when switching between the two views, scroll position is never the same... meaning the first visible game is not the same in grid view as in list view after a switch, same if going from grid view back to list view. Not a big deal, just something you would automatically expect... thinking about it, it does make sense in a way... determining which game shows as first in either view is probably no simple thing, and calculating the scroll position to have both views show the same game as first visible one... probably a nightmare...
