soffes / clock.saver Goto Github PK

Hi Sam,

I like your screen saver and prepared a caskroom formula for it. However, the pull request is currently on hold, because your latest release has been a while. Are you planning a new one soon — perhaps going to swift 4.1 could already justify a maintenance release? 🙂

Clock-saver displayed in my Mac rather on grey background then black. I have no problems with other screensavers which give me real black colour. For example native "Message" screensaver. May I ask a solution?

After I choose a clock in the options, I can't go to the options again. The area is blank. I've to quit the system settings and open it again, choose the screensaver again. Now I can change the settings. Understand? Otherwise here's a small screencast:
https://www.screencast.com/t/Ymu7fxsRsDs

clock 0.7.0
macOS 14.6

cheers meisterleise

When I activate the “Show Braun logo” checkbox in the settings, the Braun logo is rendered in front of the hour hand (only visible around noon and midnight of course).

Would you be open to have a more analog-like animation? Something like this: https://www.dropbox.com/sc/mksyksz1xm5wzmu/2KQqciTZjC
The downside is that it requires a higher framerate, but I think it looks cool. Maybe have it as an option?
If you think you'd find it interesting I'll send a PR.

This is the error I get every time I try to compile and add the screensaver to the preferences. I’ve also been trying to make my own screensaver for the past few days but I can’t get past this incredibly frustrating error myself. How did you fix it?

Edit: I’m making sure “Always Embed Swift Standard Libraries” is YES and Principal class points to the only class I have written so far. Also, weirdly, the downloaded .saver file works correctly but compiling the code on Xcode 9.3b4 and running on 10.13.3 doesn’t.

The latest release has the hour hand bug :)

Thanks for the beautiful screensaver. Could you maybe ad a version without the second hand?

Tried installing it using latest macOS. Got an error:

“Clock.saver” can’t be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information.

Select the screen saver option and click ok. Click the screen saver option again, a white screen bug appears. Hope to fix.

I prefer BN0021 and BN0032 models in black, of course. But I find the background color in dark styles is grey with some kind of a purple hue.

Even though it looks nice as it is, I can't help but wish there was an option for a totally black/dark style—call it triple black or double dark. With the mini LEDs on the new Mac model, I say it would look pretty sick.

First off, let me start by saying that this screensaver is beautiful. It's perfectly executed and I'm seriously impressed. We have it running (mandatory) for all the computers in our office and it looks elegant AF.

My questions arises around having an option to show a custom logo or piece of text on the screensaver. I don't want to ruin the aesthetic, but perhaps text or a logo in the same vein as the braun logo.

Let me know your thoughts on this and if it's something you have considered. Since this is open source, it might be something we can build a PR for, but I wanted to get your input on it before we undertake that effort.

Thanks!

If the screensaver is active and I switch from an external monitor to the display on the macbook pro, the clock is no longer centered. This seems to have started with 0.5.

Let me know if you need more info.

Hello!
I've recieved a notification that the code signature has changed between version 0.7.0 and 0.7.1
can you confirm this?

EXPECTED Nothing Magical Inc. (UP9C8XM22A) but FOUND Apple Development: Samuel Soffes (F5W43ET9UG)

Thanks!

A Homebrew user reported that the installation fails because of a checksum mismatch on the current version 0.7.0 of Clock.saver. I can corroborate:

==> Downloading https://github.com/soffes/Clock.saver/releases/download/v0.7.0/Clock.saver-0.7.0.zip
==> Downloading from https://objects.githubusercontent.com/github-production-release-asset-2e65be/17547174/6c9e3172-023c-4e1e-833d-998e49c0751a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211206%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211206T101935Z&X-Amz-Expires=300&X-Amz-Signature=7ff421687218baf94dcef72dae406aee03f7e85e7ce2a9668e67637200fcf2c3&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=17547174&response-content-disposition=attachment%3B%20filename%3DClock.saver-0.7.0.zip&response-content-type=application%2Foctet-stream
Error: SHA256 mismatch
Expected: 9497e774695cadfb25fb6ad1b5689a110f806041b34d3b536b862d653de8bca4
  Actual: a5559b1bcb20ae5bc473e16e6842618aa3a51ed17e9dc583a069ed1af5931180

The latest change on the cask definition was:

df911976cc 2021-03-21 05:06:19 +0100 clocksaver: add livecheck (#101682) Markus Reiter.

Checksum was confirmed good by CI then. Did you update the file in place since then or is something else going on?