dustinrue/ControlPlane — comment on commit 929a5ae1b8fac266cfeeb2b789264a38f47d21d2
File: Source/TimeMachineDestinationAction.m line 103
By dustinrue:

It was a "debug" sleep and I've been going between two different machines so I was moving around using git.

Here's the deal, I'm losing this battle with distributed notifications because the even though I'm trying to use a singleton that should be on a background thread it never actually receives the response so long as I'm still in limitedOptions. The moment I leave that method the responses come in. So in the current state, if you have Tedium running and configured with at least one destination and then you load up the new action screen it will be empty the first time and then contain data if you run it a second time. As of right now, I'm not sure I can make this work.