You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the list of similar Kanji feels rather random.
Kanji that are not yet unlocked are mixed between Kanjis that have been already learned.
This results in big eye jumps especially on large screens, making it a bit harder to spot differences between Kanji.
Proposal
Order list to show already learned items first, then locked ones after.
I can think of 2 ways:
check if Kanji is yet unlocked, and if not, put it at the end
order by WaniKani-level
The text was updated successfully, but these errors were encountered:
marciska
changed the title
Request: order similar Kanji by level/availability
[似合い] Request: order similar Kanji by level/availability
Jan 13, 2023
Currently, the kanji are sorted by a "similarity score", so the ones one the left should be the easiest to confuse. I'm not against moving the not yet unlocked ones to the end, but ordering by WK level would break the "pin kanji of your choice to the top" functionality, because atm it just adds a big boost to the score.
You are right. I made a pull request a while ago, but changed it now according to your suggestion. Sorting into two groups of (A: unlocked Kanji, B: locked Kanji), and sorting both groups by their score rather than their level makes more sense to me.
In any way, the gaps between kanji I learned and have not yet learned are quite distracting for me, but I'm happy to accept everyone else's opinion.
Right now, the list of similar Kanji feels rather random.
Kanji that are not yet unlocked are mixed between Kanjis that have been already learned.
This results in big eye jumps especially on large screens, making it a bit harder to spot differences between Kanji.
Proposal
Order list to show already learned items first, then locked ones after.
I can think of 2 ways:
The text was updated successfully, but these errors were encountered: