llMinEventDelay INFO

[steph Arnott]

Touch triggers two times, before the limit and then at the end of the limit.

Touch_start triggers once untill the limit ends.

Touch_end triggers at the end of the limit.

 

[Rolig Loon]

No, touch triggers a zillion times, as long as the mouse button is held down.  If you use llMinEventDelay, it only allows the touch event to trigger one time during the delay interval.  So, if you use llMinEventDelay(5.0), for example, you can hold the mouse button down as long as you like and the event will only trigger once every 5 seconds. If you release the mouse button during an interval, you will see a response at the end, but what you are seeing is the result of the button having been held down.  It is not being triggered by releasing the button. 

(1) Touch triggers a response, delay period starts

(2) Mouse button is still held down, so the event is being triggered repeatedly, but cannot respond until .....

(3) Five seconds later, it responds to one triggering impulse that happened during the delay period.

[steph Arnott]

Simple, just try it with touch, touch_start and touch_end. The script is what 10 lines?  Touch trigger two times, touch start  starht away and touch end after the limit. This is not a complicated script so there no other things happening to mess the results.

[Qie Niangao]

Right, touch() is triggered with touch_start() and touch_end() and only if the mouse is held longer than llMinEventDelay, standalone touch() events happen too.

I never really thought about it, but it's helpful for script logic that all the touch() events are reported after _start and before _end, even the ones that are essentially redundant with _start and _end.

[steph Arnott]

Which is probably why the two state bug exists, the post inputs are never cleared from the queue as the last input trigger _end removes the precceding one and itself.  Not a very tech way of saying it, but thats the gist of it.

TYPO