Is your feature request related to a problem? Please describe.
Not a major problem, just a quality of life tweak or perhaps minor bug.
Describe the solution you’d like
Ideal Behavior
When adding image occlusion cards, the translucency toggle setting (shortcut key: L) is remembered. So if the translucency is set to be opaque, adding additional image occlusion cards has that opaque setting selected as default, my occlusions will be opaque, and it will stay that way. If I change the setting to translucent in a new card and add the card, the next card I create will now have that translucent setting selected as default, my occlusions will be translucent, and it will stay that way.
Problem
However, in the card browser, this setting is not remembered. Instead, it defaults to opaque even if I change the setting. So if I’m viewing an image occlusion card in the browser and I toggle the translucency to translucent, the occlusions will become translucent in that card. But if I select another image occlusion card in the browser, the occlusions will be opaque again.
Solution
Make the card browser remember the translucency setting I set it to, just like the add card behavior currently does.
I would love this feature also. I just started using IO for organic chemistry reactions, and now my card browser is full of images where I have occluded every element of the image and thus have no idea what is on any card until I manually turn on transparency mode every time I change the card. This makes it very hard to find any cards in the browser without additional fields for this purpose… but those fields don’t show by default either because clicking a new IO card causes the fields to disappear from view and just show my entirely occluded images! Very inconvenient!
Hello, I’m new to Open Source and I would really like to contribute to Anki. I’m considering tackling this issue as my first contribution. I just have some questions:
Is this issue approachable for a first constribution, or it can be harder than it looks like ?
Do you think this issue has significant chances to be merged if done correctly (because it looks like a feature suggestion) ?
For future reference, should I ask those types of questions on Github or on this forum ?
Quick update, while waiting for feedback, I took a quick look and I think I’ve found a solution which involves very few line changes and reuse existing functions and variables.
I’m a novice at programming as well so wanted to wait for others to answer (they might need a week or two to see your question though). But regarding this:
Dae is the main developer of Anki and has opened a Github issue for this suggestion. That tells me that dae is open for this feature to be included into Anki. Maybe dae will ask you to change a few things when the PR is opened, but I don’t think you’ll have to worry about dae straight up not wanting to merge a PR that solves that issue.
