-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: 'wallpapper.InputFileNotExistsError'. #8
Comments
I cannot replicate this. I added more information to the console log. Please grab new source code and execute it. You should get more information on console. Maybe this will help us with this bug. |
Cool, I should have some time to do this tomorrow 🙂 |
Did you manage to run improved application? I would like to close this issue. |
I got the same problem, fixed it by renaming the folder I was in into something without spaces. |
Thanks for your feedback. I added support for absolute paths. It's working with paths with spaces: wallpapper -i /Users/mczachurski/Projects/Wallpepper/earth\ wallpaper/wallpaper.json and without spaces. Also relative paths works: wallpapper -i earth/wallpapper.json Please verify my fix. |
I can confirm it worked! 😄 this is awesome. By the way, the reason I wanted to use the Solar Gradients JSON data is because I started with it as a template and worked backwards to recolor various photos to look like different times of day according to the Solar Gradients wallpaper. It looks perfect! It would be convenient if the Solar Gradients data could be included by default, that way the script could just take any folder with images numbered 1-16 and optionally a json file if you want to customize the solar behavior. |
Finally got the json file made, but when attempting to run
wallpaper -i filename.json
I get the following error :Error: 'wallpapper.InputFileNotExistsError'.
I'm on Mojave DP5. The json file is definitely in the folder with the rest of the images and I'm referencing it with the correct name. In addition, I double checked all the files referenced in the json file and they are correctly named, too.
The text was updated successfully, but these errors were encountered: