Hi,
I made a macro "Mute for 60 minutes", basically 3 commands (mute, wait, unmute) and I believe it didn't survive the restart while waiting for the next command so I ended up with the muted state one hour later. I suspect that it is too much to ask for a ongoing macro to survive, is it? So if I want it to be "atomic", I'd rather make something like a two-macro series, when the first one writes some deadline time and another one periodically reads this file for the end command to be performed. Other ideas? Actually, it's not a big deal, maybe more like a interesting challenge
I made a macro "Mute for 60 minutes", basically 3 commands (mute, wait, unmute) and I believe it didn't survive the restart while waiting for the next command so I ended up with the muted state one hour later. I suspect that it is too much to ask for a ongoing macro to survive, is it? So if I want it to be "atomic", I'd rather make something like a two-macro series, when the first one writes some deadline time and another one periodically reads this file for the end command to be performed. Other ideas? Actually, it's not a big deal, maybe more like a interesting challenge