Image occlusion should create multiple cards
Closed this issue · 5 comments
I’m not sure if (1) this is supposed to work already and it’s a bug or I’m doing something wrong or (2) this is a feature request.
Describe the solution you'd like
When I create an image occlusion block with different occlusion IDs (let’s say 1, 2, 3) created in the image occlusion editor, I would like this to create 3 cards in Anki – this is what I expected when I saw this really cool feature.
Describe how it will help your workflow
Currently, this creates only 1 Anki card for me. This means that I can’t separatly train and memorize the different pieces of information occluded in the picture (1, 2, and 3).
I am unable to reproduce this.
When an image occlusion has different occlusion IDs, the plugin creates a single Anki note containing multiple cards. Are you perhaps confused between notes and cards?
Hmm no, I’m aware of the distinction between notes and cards.
I did some testing now and I discovered that most of the cards that were created, strangely, were marked as ‘suspended’ and/or ‘buried’, even though I never marked them for that. Unmarking them made everything work now, however.
Plus, new cards aren’t marked for buried/suspended now and work fine, so I guess you can close this issue. I still don’t really think that I did anything wrong when I added the previous notes, but if this was a bug, it seems to be resolved now 🙂
Thanks again for this cool plugin!
I just studied one of the image occlusion notes again and the same thing is happening: when reviewing, I’m only shown 1 card, after that no other cards from that image are shown to me anymore.
The Anki message seems to suggest that all other cards are buried:
Is that correct? And the expected behaviour? If yes, why?
@wuqui Somewhat late but the issue you are describing suggests that the "Bury new siblings" toggle is on in your deck.
Thus cards are created as intended but when they are imported in Anki (specifically your deck) they end up buried since the cards of an IO-Note are siblings.
Yes, I think that’s the reason for the expected behaviour. Forgot to post an update here. I’m gonna close the issue since it’s not related to the plugin. Thanks.