Forums Feature Suggestions ON TIMEREND

Hello,
As the subject implies, I'd like to propose the idea of adding an "ON TIMEREND" event. I'm sure I don't need to explain why, as the name explains it all, but I personally would find it to be very useful; take it for what you will.

I don't see much use for an event like this, considering you can execute a command on a timer anyway.

Realistically this already exists, as the command given in the timer line only gets executed when the timer ends, per hixxy's example.

Furthermore, if one uses a number of repetitions other than 1, one can check $timer($ctimer).reps in the called alias; if it returns 0, you're in the last repetition, ie at the same point in time as the suggested on TIMEREND would be.

I too was thinking the OP wanted an event to be triggered
when a timer executes, but after reading qwerty's post it does
sound more like he's requesting TIMERHALT or TIMERSTOP. This
would make more sense as I was scratching my head before
wondering why this would be needed.

Not sure of the OP intentions here, but maybe it was a more generic reasoning, for tracking timer activity for instance?

In such a case something like this might be more useful... although personally i cant think of where i might ever use it :s

on *:TIMER:EVENT:TNAME: {} with an identifier containing the timer name so it can be used with existing timer identifiers. (event=start/rep/end/off/whatever)

Not for or against the suggestion, but i dont see much use for it other than possibly script debugging.

If the reason you want this is for multi-line timers try placing signals in a timer. But remember parameters passed when starting the timer are evaluated before the timer begins.

/.timer 0 1 .signal MyTimer

you can pass parameters bij using $!something if you don't want them to be evaluated on the start of the timer