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
You can tap okay and get the result "No cards matched the criteria you provided"
I understand that this knowing if the criteria is matched is asynchronous. In some case, I guess it can be slow to know whether "ok" would do anything or not. I assume however that in a lot of case, it'd be quick to either see whether "ok" would lead to more reviews or not.
Because, right now, I find it slightly absurd that Anki (and ankidroid) requires me to tap on "ok" to be able to learn something that it could have told me earlier.
My suggestion would be:
when the criteria change, start checking whether "ok" would lead to reviewing more cards
if after .2 seconds (or some other standard delay), no answer is found, enable "ok" button, (maybe with a spinner instead of "ok")
when the answer is found, enable or disable (and remove the spinner)
The text was updated successfully, but these errors were encountered:
how to reproduce:
Expected result:
Actual result
I understand that this knowing if the criteria is matched is asynchronous. In some case, I guess it can be slow to know whether "ok" would do anything or not. I assume however that in a lot of case, it'd be quick to either see whether "ok" would lead to more reviews or not.
Because, right now, I find it slightly absurd that Anki (and ankidroid) requires me to tap on "ok" to be able to learn something that it could have told me earlier.
My suggestion would be:
The text was updated successfully, but these errors were encountered: