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
{{ message }}
This repository has been archived by the owner on Dec 30, 2020. It is now read-only.
This isn't big deal; only aesthetic. To reproduce, just type into the search really quickly. Preferably, type in a word that are in a lot of song names. While it tries to live-filter while the typing is happening, sometimes the wrong song pictures get associated to the final results.
The text was updated successfully, but these errors were encountered:
Yeah, I noticed this bug already, you're right, this happens when we type fast. I'm pretty sure it's because of the order of the async event. At each letter, it does the filter and asks for a new image. And sometime the previous search was slower than the new one, resulting in getting the wrong image.
@DanP27 Yes, as you can see the commit referenced above (68e7987) is fixing the issue, however, it's planned for the next major release. (v1.1, which I'm working on it since months on my free time 👌 )
You can see the work done (and try it if you know the tools) on the feature-beatsaver-integration branch.
This isn't big deal; only aesthetic. To reproduce, just type into the search really quickly. Preferably, type in a word that are in a lot of song names. While it tries to live-filter while the typing is happening, sometimes the wrong song pictures get associated to the final results.
The text was updated successfully, but these errors were encountered: