can you explain what you mean by allowing for more precise triggering of the alert? i just like hearing about development. ;-)

i am going to use it for what i intentionally downloaded it for, it was just this situation with the paceoftape indicator that was hanging me up..

anyways, thanks again for your help and all of your coding!

The original concept was a zone for price. Alert triggered when alert - (n+1) Ticks < price < alert + (n+1) Ticks, where n is the offset to be entered in ticks. This concept has two shortcomings.

(1) When price moves fast and no trade is printed at the alert level, no sound alert is triggered, although price croessed the alert level. So it is not enough to check whether price has printed inside the defined range or - in case that the offset is 0 - at the alert level. In parallel it needs to be checked, whether price has crossed the level. This event will also trigger an alert now.

(2) The concept with the ticks, requires discrete prices, which is the case for all instruments. Indicator values however are more of a continuous nature - actually they are also discrete, but the discrete levels are unknown -, and therefore the inegality above cannot be used in the same way. So I changed the above inegality to alert - n * units <= price <= alert + n * units. If you set the offset to 0, the indicator will only trigger an alert, if the indicator exactly hits the alert level. As the indicator values are discrete, this is unlikely to happen, even if the indicator value has crossed the alert level. But with the modification introduced under (1), the crossing of the line will trigger an alert on its own, so this is no problem.

Hope, I managed to confuse you and all other readers of this post.

fatty have you given my idea any thought? what new stuffs you been working on? whats up dood!?!?

I am still waiting for feedback, had made some other changes.

I am still waiting for feedback, had made some other changes.