掲示板 Forums - Improving the "Meaning->Kanji" vector on quizzes

If I recall correctly, the reason I am not using the Meaning->Kanji vector on my schedules is because Meaning->Kanji expect the user answer to be given from a list with multiple choices.
This had led in the past into situation in which I recognize the correct kanji answers either because I can associate a kanji with the meaning, or because I excluded the other 3 answers. This meant I could pick the correct answer, even if I had no idea of how it was pronounced, leading to a not very beneficial training.
Right now I am using ""Meaning->Kana", which forces me to type out the word, actually forcing me to recall it, which in my opinion is definetly an improvement.

The problem is that even though I recall the pronunciation, sometimes I cannot recall the kanji for the life of me, so even if I get the answer right, I can't really say I am proud of having passed the test like that.

So what I'm proposing is having both in one, basically a ""Meaning->Kanji" vector which expects me to type out the answer in kanji. That way I would have to first recall the pronunciation in order to write it, and then to choose the correct kanji. Would be a stricter test and overall a more beneficial and more rewarding one, I think :)

I am not sure what do you mean, how do I enable fill-in-the-blank ?

I never noticed this before xD

There is only one possible small problem with it, since there are questions that do not have a kanji answer, one is forced to turn on "Meaning question → Kana answer"  just to be able to answer to those in the quiz.
Does it mean now I am doing all the schedule content as "Meaning question → Kana answer" as well?
If that's the case, then it is a problem.

The optimal situation would be to treat all vocabs that can be answered with a kanji answer with the Meaning->Kanji vector, and then to let fall off to Meaning->Kana only those that cannot accept a kanji answer.  
But answering all in both vectors is just redundant, I think :/

I'm not planning on having a "conditional" vector that turns on to cover cases like that - it would make the schedule's engine go all crazy. Sorry! If you have meaning > kanji and not meaning > kana, then it WILL not study meaning > kana for terms without kanji.

You could setup two schedules with the same terms included, one setup to only do meaning->Kanji and the other meaning->Kana; The former will never ask you any of the terms that don't have any Kanji while the latter would ask you for Kana of everything (even if there would be Kanji included).
To ensure that you get the most out of the Meaning->Kanji vector every day, you would then just have to make sure that you do the Meaning->Kanji schedule first/before you do the Meaning->Kana one.