You can create a separate table and select the “Kana Only” option in the Item Type filter.
1 Like
Found it, thank you!
1 Like
I just found this script and am still figuring out its full capabilities/limitations, so I apologize if this is a fairly basic question: is there a way to create a filter that shows last review failures plus any items that are visually similar to those review failures?
I can see how to make a filter for last review failures, or to use Related Search to make a filter for items visually similar to a specific manually-configured search query, but is there any way to compose the two somehow? (Ideally I’d like to study and/or export not just recent failures, but any items that I’ve learned that are visually similar to those failures as well)
1 Like
You can make a table for Failed Last Review and apply the Leech Training Emulation toolbar button to it. This will add up to three similar items for every item to the table. There are settings to determine what is a similar item and other features of the Leech Training Emulation algorithm…
1 Like
This isn’t working on my m series macbook. I have the kanji stroke order font installed into my mac fontbook but it keeps saying its not installed no matter what I do. See image.
2 Likes
There is a limit to how much I can do because I don’t have a Mac, therefore I can’t reproduce problems on my end.
There are two things I can tell you.
Did you try rebooting the computer? There is a similar problem on Windows that causes installed font not to be recognized by the OS until the computer is rebooted. I don’t know about MacBooks but it is worth a try.
@TreyE reported an issue with Safari/Webkit which cause the browser to be unable to use local fonts. This is intentional because the Apple guys have decided this is the way to fix a privacy issue. Changing browser doesn’t help because on a Mac every browser use the webkit rendering engine to comply with Apple rules on Mac software.
The only workaround is to disable the Stroke Order font check message Once this is done you still won’t have the font installed but at least the annoying message will go away. This is done by turning off the Show Stroke Order Popup check box in the Item Inspector settings in every table and every view. This will cause the missing feature message to disappear. Make sure that the check box is turned off from every table and every view otherwise the message will stubbornly remain.
Firefox with strict ETP also falsifies the font list as an anti-fingerprinting measure
2 Likes
The font update has made the tiles look a little wonky due to the font-size being set to 30px. I recommend changing it to var(--font-size-large, 24px);. The variable is what WK uses on the dashboard for the tiles in the progress section, and it has a fallback of 24px in case something happens to that variable. This way, any further changes WK makes to that variable will be applied without needing to update the script and if something happens to the variable entirely the styling doesn’t default to inherited values.
Edit: maybe add font-weight: var(--font-weight-regular, 400); as well.
The selector should be #WkitTopBar .WkitItemListed.
Version 1.26.5 is available - Please download it at the link in the top post
Fixes the ugliness resulting from the recent Wanikani font change.
1 Like
Version 1.26.6 is available - Please download it at the link in the top post
Further fixes the ugliness resulting from the recent Wanikani font change.
1 Like
Version 1.27.0 is available - Please download it at the link in the top post.
This version implements custom icon to prepare for the upcoming phase out of the current Fontawsome icons by Wanakani. It also implements a new filter to select radicals that are displayed through SVG images.
1 Like
Ah, is it possible to remove the fill="#000000" attributes on the <rect>s in the Settings cog svg? When using a dark theme you can’t see the teeth of the gear because they’re all black while the body is the lighter text color.
1 Like
Version 1.27.1 is available - Please download it at the link in the top post.
Fixes the cog wheel icon as requested by @LupoMikti
1 Like
Version 1.27.2 is available - Please download it a the link in the top post.
Fixes a bug preventing audio from playing.
1 Like
The recent dashboard update broke Item Inspector. The problem is not trivial. It will take some time to find the solution. Please be patient.
5 Likes
the problem is trivial - wk just went and broke all the scripts again 
It’s the solution that’s the challenge
hopefully you can find a solution (wk removing 167,000 lines of code seems like uhhh) a nightmare!
Seriously though!
I’m so grateful for this script (would have given up long ago if couldn’t export)
Thank you for all you help back when I was level 44. This script is what kept me doing wk (via kitsun lvl 58 right now) almost level 60 (and exported before all that silly kana vocab silliness.)
Only 5 1/2 years and lots of script breaking by wk dev team over and over again.
I swear they should be paying all of the script and app writers.
Best of luck and hopefully you can get this one working! It was one of my favorites
2 Likes
Ok, the problem seemed bigger than it actually is. Essentially there was one big issue to tackle and one smaller issue to tackle.
(1) The removal of JQuery. Thankfully Open Framework comes with JQuery, you just have to include it. So near the bottom I change the include and Promise.all to:
wkof.include('Jquery, ItemData, Menu, Settings');
// parallelism to reduce startup latency, especially if network transfer are involved
// There is not much to gain because this is mostly disk access on the same disk
// but every little gain counts.
Promise.all([loadPrerequisiteScripts(),
wkof.ready('Jquery'),
wkof.ready('Settings').then(function(){return wkof.Settings.load(scriptId)}),
wkof.ready('ItemData, Menu'),
])
.then(loadItemsFiltersAndDb) // must be after prerequisite scripts, ItemData, and loaded settings
.then(initSequence)
This brought a new issue wherein there are two instances where $ is used before the include and promise. So I needed to replace those two instances with vanilla javascript.
On line 229 (for me), change to:
var userstyleItemTextColor = window.getComputedStyle(document.querySelector('.subject-character__characters'))['color'];
On line 10167 (for me), change to:
var $script = document.createElement('script');
$script.textContent = script;
(2) After this, the small issue is the position array. I fixed this for Heatmap as well, since it looks to be the same array.
let position = ['.dashboard__content', '.dashboard__srs-progress', '.srs-progress', '.dashboard__item-lists', '.dashboard__content'][quiz.settings.position];
if (quiz.settings.position == 0 || quiz.settings.position == 1){
$(position).before(sectionContainer);
} else {
$(position).after(sectionContainer);
};
With just these changes everything should be back to working as expected. Please feel free to clean up these solutions as needed.
4 Likes
Version 1.28.0 is available – Please download it at the link in the top post
Fixes incompatibilities with the new dashboard. The script should work again.
Thanks to @LupoMikti for their contributions.
5 Likes
I have noticed the layout of table mode is broken. I am working to fix it. In the mean time the itemlist mode works fine.
3 Likes
Ah, my apologies for not checking that layout. I only ever use itemlist mode so the thought didn’t cross my mind to check.
2 Likes