Skip to content
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

Running Mac OS Catalina: Select file or directory button not working #61

Closed
irishgerman opened this issue Feb 10, 2020 · 1 comment
Closed

Comments

@irishgerman
Copy link

I really like this program, and it was a shame when I couldn't select the gifs I wanted to use, I would click the button and it would light up and do nothing. Hopefully, this issue is fixed!

@Waitsnake
Copy link
Owner

Me too. It was a shame when I saw that Apple had restricted the classical Screensaver API with Catalina as they put the screensaver process that runs the Screensavers into a restricted sandbox that limits the things an Screensaver is allowed to do. A Screensaver is no longer allowed to read local files or even let the user select the files he want use. This behaviour can only changed by Apple.

Maybe Apple did this for security reasons? But ironically a Screensaver is still allowed to load GIFs from a web address witch seems more dangerous to me than reading a local file. Therefore one chap on Github had made a fork of this project that allows the user to add a web address to a GIF instead of a local file. If this fork fits your needs it can be found here:
https://github.com/arneson/gif-screensaver

As for my part, I prefer to wait for Apple to fix the Screensaver API, as I prefer to load my GIFs from the local directories rather than from the web.

Apple itself already uses a new API (appex files) for its own screensavers in Catalina, which do not have these limitations, but this API is not publicly available. And so I play the waiting game until they fixed their mess. But since it hasn't been repaired in the last 4 months, I guess it will only be with the successor of Catalina.

I will close this issue here sooner or later since this is already the fourth issue we have for the same problem, see #57 , #59 and #60 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants