Title: XXHighEnd Model 0.9-y3 - Gallery Cache Post by: AUDIODIDAKT on September 05, 2009, 03:33:23 am Gallery is absolutly as fast as it can gets, :o
So, max Thumbnail Cache Size = 1920 Amazing! But it works a little strange, have to point this out! (caches only 1 genre at the time) Why not keep all in cache. Title: Re: XXHighEnd Model 0.9-y3 - Gallery Cache Post by: PeterSt on September 05, 2009, 09:34:06 am Hi,
I am not aware of a maximum size, unless your memory limits it. Otoh, 1920 :scratching: ... maybe you are right (I checked up to 1000 so far). Then, I never though of letting it work over the boundaries of Galleries themselves (what you call genres). So, it gets reset at specific situations, and without much thinking asking for a new Gallery is one of them. But I don't think it's really necessary ... (and worse : what about asking for a redundant genre, like Women vs. Jazz, and the redundant pictures would just be resused. Always room for improvement. So keep it coming ! Sidenote and FYI : Only after two years it came to me how I could solve an inherently stupid MS approach of things, and although it may be more intelligently solved by them for my brains to get, when you scroll one step, all the pictures you see in the visible area are being retrieved 20 or so times. A few outside the visible area as well, a few from the very bottom, the top ... Net, this is far better than the Checkboxes method (which really won't work when you have a somewhat more albums in the list), but it can be 100ds of times more efficient. The basic principle couldn't be tweaked for the better, but fooling everything by letting it come from a "cache", could. Btw, maybe you have tried to make the pictures smaller so more would show up, make the screen larger so again more would show up, to come to the conclusion that the thing never could finish showing everything; At half or 3 quarter of the screen it reshowed. Again and again; That too is very smart, because maybe a picture has changed in the mean time, or whatever it is ... that just did not work. The same principle is still in there (try it) but now at the second time it works, because a seond time now will blast everything on the screen from the cache at once, and the timer (which is what it looks like) now just comes too late at attempting to reshow the screen (so that timer would run off before the screen was full). Peter |