-
Notifications
You must be signed in to change notification settings - Fork 3
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
Remember language and destination field for each deck #27
Comments
Oh, nevermind, it already has something similar: |
Small addition: It works by tagging the deck with the language code to later use as reference. Disabled by default since people may not be ok with their decks getting tagged without knowing what could cause it. To be honest it should just be a config only lookup, but what worked works.
Yup, I understand that an actual option menu would make it easier to find, but I figure those that require customization to that extent are bound to find it in the config (more honestly, my busy and lazy behind has not come around to it and just relies on the anki config.json). Now for the destination field, my inital reaction is hessitant. Do people really use different types of cards for learning different languages? I assume they'd settle on a single (custom) card profile to suit their needs. |
Hey, it's me again. Any plans to make the add-on remember the destination field for each note type? |
Suppose I have deck A and deck B with different languages. Right now when I want to add audio to a card from deck A, I have to select the destination field and the language, and if afterwards I want to audio to a card from deck B, I have to re-select the language and teh destination field.
Solution: add a "Save preferences" button. It will save the destination field and language (for this deck) in the add-on configuration. That way users won't have to switch back and forth between languages and destination fields if they are learning 2 or more languages, or using 2 or more different decks with different field names.
The text was updated successfully, but these errors were encountered: