-p doesn't actually pause a timer
which is why I made this report.
It basically just silences the output until it's resumed
Pausing isn't "silencing the output", not sure where you got that statement from but the point of "pausing" is that the state of whatever you are pausing remain unchanged until you resume it, when you pause a song, you don't expect $insong.pos to change so when you pause a timer you don't expect $timer().secs (or .reps) to change.
If you truly pause a timer, then your times are messed up when you resume it. For example, if you have the timer going off every 30 minutes (let's say at :00 and :30) and you pause it at :45 for half an hour, then resume it, your timer will go off at :15 and :45 from then on. That is probably not what you want to have happen.
What you are saying doesn't make sense, of course that's what I want to happen, otherwise I wouldn't have paused the timer in your example, I also wouldn't have made that report..
I believe Khaled has responded about that in the past.
Hum, it would be interesting to see what he said, btw, I found the post I was referring to in my first post https://forums.mirc.com/ubbthreads.php?ubb=showflat&Board=8&Number=154009&Searchpage=1&Main=28732&Words=timer+%2Bpause&topic=0&Search=true#Post154009.
Of course, there are valid reasons for it to really pause and valid reasons for it to silence output while "paused."
Ah ah really ? Can you give one example where it makes sense and where one could use the actual behavior ?
