I had a theory that the freezing part of this issue https://github.com/amiantos/multiclock/issues/6 was because of my use of NotificationCenter.default, namely that when firing the 'animationComplete' messages, they were being received by both instances of the screensaver, which made things get wonky. I didn't do anything to prove this theory, beyond the work of this PR.

I removed any usage of NotificationCenter and replaced it instead with completion handlers. It seems like this fixed the issue with multiple instances of the screensaver as well as fixed a millisecond or two delay when progressing through the animation queue, which is a nice benefit. Overall much better to do it this way, though it did mean I had to add a bunch of completionHandler arguments to stuff in the Animation file...

• change version number for screensaver to 1.1
• fix offset modern (thick) dial
• replace modern (indices) dial
• replace shout hands
• add LCD style hands
• add traditional style hands
• replace apple watch hands (new version has transparent center hole for bg color to show through)

Consider adding to ClockScene.swift:

    /// without this, it beeps on every keystroke, recognized or not.
    override func keyDown(with event: NSEvent) {
      if let character = event.characters {
        switch character {
        case "c","o","p","q","r","t","w":
          break
        default:
          super.keyDown(with: event)
        }
      }
    }

Added some new patterns (including some random position generators) and animations... also removed the Int.random() call and replaced it with a preset array that is shuffled() at launch and then run through repeatedly, to avoid animations playing too frequently.

• some existing animations can be improved (check out how the inwardPointPattern resolves itself in the demo gif/video in the readme compared to how it resolves itself in the actual screensaver for an idea)
• I'm sure there's plenty of cool animations and patterns to come up with and add

I'm not sure if it's just my MacBook, but when the screensaver is running on the internal Retina display, the frame rate and behavior can be really weird. Doesn't happen on the lower res external monitor. Maybe there's a memory leak or something? It's weird no one else has opened an issue about this, though...

I have a dual screen via Display Link and my second Display Screen is a few miliseconds delayed. So I have observed that on one screen it was 9:19 and the second 9:20.

After a build using git clone as of this writing, with the macOS target:

multiclock/Shared/Nodes/Assets.xcassets:1:1: The image set "thumbnail" has 2 unassigned children.
multiclock/Shared/Nodes/Assets.xcassets:1:1: The file "[email protected]" for the image set "thumbnail" does not exist.
multiclock/multiclock/Shared/Nodes/Assets.xcassets:1:1: The file "Thumbnail.png" for the image set "thumbnail" does not exist.
Ambiguous Content Group
multiclock/multiclock/Shared/Nodes/Assets.xcassets: warning: Ambiguous Content: The image set "thumbnail" has 2 unassigned children.

Missing Content Group
multiclock/multiclock/Shared/Nodes/Assets.xcassets: warning: Missing Content: The file "Thumbnail.png" for the image set "thumbnail" does not exist.

multiclock/multiclock/Shared/Nodes/Assets.xcassets: warning: Missing Content: The file "[email protected]" for the image set "thumbnail" does not exist.