You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user goes into a folder with (say) a dozen movies, the thumbnail for some movie that happens to be generated first is used for other movies.
Not sure the order, but some file starting with R got their thumbnail done before one starting with A. The file starting with A has no thumbnail, then .. it surprisingly gets the thumbnail of the file starting with R, which is obviously the wrong thumbnail.
This is not a huge issue, as it appears that the algorithm used here is self-stabilizing, but I'm filing this to
verify that it's self stabilizing and the right thumbnail ends up in the right movie. is it? yes or no?
is it easy to correct this temporary bad assignment of the wrong thumbnail?
The text was updated successfully, but these errors were encountered:
I'm not able to reproduce this.
In issue #190, we had the problem of thumbnail regeneration which also caused the disappearance of thumbnails on scrolling, but seems like it's working fine now (thumbnails.
I tested: a folder containing 50+ images, a folder containing 20+ songs, a folder containing 15+ videos & a folder containing several file types.
@Marton-Zeisler could you check and see if you're able to reproduce this behavior?
I have tested this app on two different devices.
That folder contained 23 images and 10 songs in one folder. I think this issue is resolved by the Pull request made by @iswiftshek
When a user goes into a folder with (say) a dozen movies, the thumbnail for some movie that happens to be generated first is used for other movies.
Not sure the order, but some file starting with R got their thumbnail done before one starting with A. The file starting with A has no thumbnail, then .. it surprisingly gets the thumbnail of the file starting with R, which is obviously the wrong thumbnail.
This is not a huge issue, as it appears that the algorithm used here is self-stabilizing, but I'm filing this to
The text was updated successfully, but these errors were encountered: