-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide an efficient way of progressively revealing cloze deletions #3637
Comments
Making a different cloze bracket syntax (like curly braces) for cloze cards that belong to each other that hides them all at the same time (progressive reveal). |
Hello, Thank you so much for creating this issue; I would like to mention that as the Alx forum user in the Anki forums thread, I am perfectly happy with a low limit that can be customized in Anki preferences with a flashing warning, especially since the alternatives would require additional coding effort. |
I agree with the previous comment. "A low limit that can be customized in Anki preferences with a warning" seems to be the best solution here. I had been relying on nested cloze heavily in my decks, so the hard limit on depth in the update created a whole new set of actual problems in order to solve "potential" problems that I never encountered in practice. |
I would strongly agree with what's been said earlier about a lower limit that can be customised. I use nested cloze cards to learn step-by-step processes, which requires the information above to be revealed before the information below. Despite the brilliant features in 24.11, this breaks literally hundreds of cards in my collection, which I hadn't properly appreciated until finding this thread, so I have no choice but to stick with the older version for now. I'd be hugely grateful for a quick resolution! |
Originally reported on https://forums.ankiweb.net/t/nested-clozes-doesnt-work-for-more-than-3-nests/52661
We decreased the nested cloze limit from 10 (protobuf library hard limit, and exponentially slower parsing) to 3 in the 24.11 release This has upset users who were already creating more than 3 levels of cloze deletions.
This ticket is to keep track of possible solutions.
Thoughts?
The text was updated successfully, but these errors were encountered: