Image Occlusion : Do not bury sibling cards (only for image occlusion)

[sorata]

I don’t think that’s always an solution though. It might not be optimal to divide your content like this; people create decks on the basis of type of content and not type of note.

Having said that, @qubist-pixel, your solution will only work for a particular note type and people will soon want this for other note types too (for example, cloze). A better solution, in my opinion, is what I describe in another thread:

@sorata

I think now it is making less sense to me that burying is attached to presets rather than note types. This feels more of a workaround as there’s nothing inherent in the essence of bunch of decks that makes you turn to a feature like burying. There can be a correlation, if you are building deck-presets in that way, that’s why it works for most people. Yet it’s the note types and the siblings that they might have which actually makes you want to use the burying feature. But I agree the current way might just be less organic (once again, proposing no change here).

(I have divided my material according to chapters/subjects and thus IO cards + clozes stay together with basic+reverse note types, becomes illogical to divide these note types into different decks/presets just for burying)

I also think the upcoming feature, “prevent sibling overlap” should be in the note types rather than the presets. See here: Native implementation of Load Balance - #57 by sorata (dang, I wrote some wrong sentences there but I can’t seem to be able to edit the comment)