Good idea. Does that previous line work for setting all monitors to the same image?
Try this for your different monitors:
cd "$(dirname "$0")"
curl -s -A "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36" -o "wallpaper1.png" "http://wkw.natural20design.com/?k=YOUR_API_KEY&d=1"
curl -s -A "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36" -o "wallpaper2.png" "http://wkw.natural20design.com/?k=YOUR_API_KEY&d=2"
osascript -e "tell application \"System Events\" to tell desktop 1 to set picture to \"$(dirname "$0")/wallpaper1.png\""
osascript -e "tell application \"System Events\" to tell desktop 2 to set picture to \"$(dirname "$0")/wallpaper2.png\""
Hello Emucat! Thank you for letting me know about this cool new 𝓀𝒶𝓃𝒿𝒾 𝓊𝓅𝒹𝒶𝓉𝑒. I’ve been out of the loop.
Yeah, an update sounds like a good idea. I have to leave for work real soon so I won’t be able to finish this until later. If you feel like helping, can you locate an ordering online that 1) follows a similar ordering that’s on the wallpaper generator, and 2) includes these characters? These are characters from WaniKani that I do not have in the wallpaper generator. Otherwise, I could always just put these new kanji at the bottom of the list ¯\_(ツ)_/¯
Unfortunately not. It’s weird, actually, like, I’m checking online at Jouyou and JLPT lists, and none of them seem to have 飴, for example. (飴 is the first one in my list above). Do you think I should just append the new ones to the bottom?
Also, I apparently had some extra kanji in the wallpaper program that weren’t even in Wanikani, lol. I’ll remove those later today.
Okayokayokay, I just posted a minor update with the new kanji ordering. Now, all the kanji shown are from and on Wanikani, and none of the non-Wanikani kanji remain.
But just so you don’t think your old friend has been sitting on his hands, you can go on to the website itself and see that it looks slightly different. More importantly, though, it looks even more different on the code side, but I’ll get into those changes more in the next major update.