Hmmm, first thought: Make the padding 0. There’s a chance the 口 is falling out of the bounds of the screen. Seems I have to do some more bug hunting if unlocked kanji are not loading sigh
Padding doesn’t seem to make a difference, neither did restarting the machine, or deleting the screensaver ( and the prefs files) and re-installing.
Poked the API with the ruby gem, to check its actually returning data, and I’ve got 18 kanji returned, with 5 unlocked (the pink ones and 口, as you’d expect)
I’ve tried with only one monitor, in case that’s skewing things, and also different values for ppi and padding ( which doesn’t seem to have any visible effect)
Oh, and removing one digital from the API key seems to manage to crash it ![]()
Thanks!
Chris
Had a little trouble finding the place to enter my API key but it worked like a charm once I found it. Thanks!
https://www.dropbox.com/s/kozbdwy8mks9q8s/Screen%20shot%202013-03-10%20at%201.33.47%20AM.png
Here is a screen shot of the menu and options button I’m having troubles with. Even after trying your most recent update, I still can’t seem to open up the options to enter my API-Key. I’m not looking through the wrong menu, right? Maybe it is just my computer that is buggy.
That is the right button you’re trying to use, my friend has a macbook with the same OSX version as you (at least the menu looks exactly the same). I had some problems getting the screensaver to work on his mac.
I’m probably going to look for my snow leopard CD and install it on an external harddrive. That way I should be able to reproduce your problem. I’ll try to fix that button sometime this week.
Sorry to trouble you with all that. Any luck so far?
MangoTree said... I wanted to keep track of my progress in Wanikani and decided to make a screensaver for that. It displays all the kanji and colors those you have leveled in the color of your level (e.g. pink for apprentice). I decided to make the layout adaptive to the screen resolution, so no matter the screen or the amount of kanji, it will scale to fit everything.What about Windows?
A picture is worth a thousand words:
Download link: http://www.mediafire.com/?mzgkrfj5eavm6ya <----
This is a big update, for the changelog check my post on page 7. You still have to enter your PPI. To find your PPI use this link:
http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density#Apple
Use the link as a guideline and tweak your PPI so that the kanji fill the screen ( should not be necessary anymore, but you are free to change the PPI to your own preferences).
Juichiro said... What about Windows?For windows I have a written a similar application, but it generates wallpapers instead of being a screensaver. /t/Wallpaper-generator/1540/1
However, you can combine my program with the built-in gallery screensaver to achieve similar results, minus the crabigator background.
I <3 you ![]()
Has anyone used this recently? I’ve just installed it on 10.8.5 and it looks great but all the kanji are still in white…
My wallpaper is crashing my system pref :\
vlava said... Has anyone used this recently? I've just installed it on 10.8.5 and it looks great but all the kanji are still in white...Im running 10.9.1 and having the same problem.
Here as well. I’m running 10.9.1 and I’m only seeing the kanji in white. ![]()
Can the kanji also be bigger and take up more of the screen? More kanji, less crabigator room?
shauntgoss said...vlava said... Has anyone used this recently? I've just installed it on 10.8.5 and it looks great but all the kanji are still in white...Im running 10.9.1 and having the same problem.
aruberuto said... Here as well. I'm running 10.9.1 and I'm only seeing the kanji in white. :-(Same problem here (all white kanji) :( bummed (OSX 10.7.5)
Can the kanji also be bigger and take up more of the screen? More kanji, less crabigator room?
About the wallpaper crashing, I don’t know anything.
The kanji are in white, because
- the WaniKani API has changed a little since the release of the wallpaper (it’s now at v1.2)
- the wallpaper script doesn’t make versioned calls to the API
so it can’t get the kanji stats.
The author only needs to make sure that the script asks for WaniKani data according to the older v1.1 API, by just changing “api/user” to “api/v1.1/user” in the URL.
(I have managed to get it working by doing this myself: setting up a proxy - e.g. Privoxy - to make the redirect, but this is a bit of a hassle.)
No matter which version I used, I haven’t gotten any kanji at all. I have OSX 10.7.5 also.
Could I have input the wrong API code? Or is my computer resetting things? Whenever I input v1.1 into the right place on the key, when I check back on it that part is erased from the URL. Also, I don’t know which resource or optional argument to add, if there is one. (I am new to API codes, but I thought I followed the instructions on the API wanikani page…)
OK, on the third try, I think I crashed it. Hmm.
Marijnn said...[...]I should clarify, by 'author' I meant the guy who wrote the wallpaper ;-)
The author only needs to make sure that the script asks for WaniKani data according to the older v1.1 API, by just changing "api/user" to "api/v1.1/user" in the URL.
(I have managed to get it working by doing this myself: setting up a proxy - e.g. Privoxy - to make the redirect, but this is a bit of a hassle.)
Dorotheian said... [...]So, trying to add the version to the API code you're entering won't work. Ideally, MangoTree would update the code :-)
Could I have input the wrong API code? Or is my computer resetting things? Whenever I input v1.1 into the right place on the key, when I check back on it that part is erased from the URL. Also, I don't know which resource or optional argument to add, if there is one. (I am new to API codes, but I thought I followed the instructions on the API wanikani page...)
[...]
Marijnn said...Does anyone know if MangoTree is still active?Marijnn said...[...]I should clarify, by 'author' I meant the guy who wrote the wallpaper ;-)
The author only needs to make sure that the script asks for WaniKani data according to the older v1.1 API, by just changing "api/user" to "api/v1.1/user" in the URL.
(I have managed to get it working by doing this myself: setting up a proxy - e.g. Privoxy - to make the redirect, but this is a bit of a hassle.)Dorotheian said... [...]So, trying to add the version to the API code you're entering won't work. Ideally, MangoTree would update the code :-)
Could I have input the wrong API code? Or is my computer resetting things? Whenever I input v1.1 into the right place on the key, when I check back on it that part is erased from the URL. Also, I don't know which resource or optional argument to add, if there is one. (I am new to API codes, but I thought I followed the instructions on the API wanikani page...)
[...]
Since the lack of colour actually bothered me (and since MangoTree seems to not be active on this site anymore), I fixed something up myself.
Here you go:
https://github.com/Compendium/wkscreensaver/releases/tag/v1.0
Since this is the result of about two nights of coding this probably has lots of bugs n stuff. Please report anything you find! (You can make a screenshot of a Screen Saver by holding Command+Shift before you hit the “Preview” button in the System Preferences->Desktop & Screen Saver pane then when the Screen Saver is loaded press “3”, and then release all the buttons. This will place the screenshot on your desktop)
I’m open to suggestions as well ![]()
Once I’m confident this will actually run on the majority of devices I’ll make my own thread.
Working fine for me! Thanks so much Greenroom!
