They were expecting that -P would pause the .secs at the number it was when the -P was issued. Instead, it's causing .secs to immediately jump up to the interval parameter as if the timer had been paused immediately after being launched. The effect is that there's no difference in pausing a 60-second interval timer at 1 second after launch or 59 second after launch.
The code I pasted in my earlier post of this thread shows this happening, with .secs jumping up to 7.
