Setting Audio Alert for Momentum

[mb3000 10]

Can anyone please help me with Easy Language code for setting an audio alert for

momentum crossing +.50 or crossing -.50 ?

 

Thanks very much.

[Tams 20]

Can anyone please help me with Easy Language code for setting an audio alert for

momentum crossing +.50 or crossing -.50 ?

 

Thanks very much.

 

what is momentum crossing?

[EasyTrader_I 10]

Hi Mb3000,

 

Paste this code at the end of the Momentum Indicator. Make sure you are making a copy of Original Indicator..

 

if Mom > 0.5 and Mom <= 0.5 then
Alert( "Indicator crossed +0.5" )
else if Mom < -0.5 and Mom >= -0.5 then
Alert( "Indicator crossed -0.5" ) ;

 

Also make sure that you have audio alert on in the format Analysis technique-->Alert Tab.

 

Good Luck..

EasyTrader_I.

[mb3000 10]

This is excellent! Thanks very much for your help.

mb3000

[statsign 10]

Mom > 0.5 and Mom <= 0.5

Mom < -0.5 and Mom >= -0.5

are both impossible - you need to decrement 1 bar

 

Mom > 0.5 and Mom [1]<= 0.5

Mom < -0.5 and Mom[1] >= -0.5

[Tams 20]

Mom > 0.5 and Mom <= 0.5

Mom < -0.5 and Mom >= -0.5

are both impossible - you need to decrement 1 bar

 

Mom > 0.5 and Mom [1]<= 0.5

Mom < -0.5 and Mom[1] >= -0.5

 

better still, use...

 

Mom cross above -0.5 or Mom cross below -0.5...

[statsign 10]

yaeh, I'm always thinking strategy coding, but for indicators using functions is fine.

In a strat calling functions takes time, crosses is a boolean that calls the math to set the boolean - 4 steps instead of one

[Tams 20]

yaeh, I'm always thinking strategy coding, but for indicators using functions is fine.

In a strat calling functions takes time, crosses is a boolean that calls the math to set the boolean - 4 steps instead of one

 

you must be from the old school...

 

50 years ago... when computer resources were scarce...

RAM were expensive, even main frame computers have limited memory onboard.

the computer scientists circumvent the limitation by offloading portions of the codes into functions, and call them only when needed.

 

many things have changed since the good old days.

not only the computers have more memory, the computer language compilation has changed as well.

when you load an indicator into the computer, the codes are compiled on the fly... all the components -- the main body, the functions, etc., are all merged into one, and the whole thing is resided in the memory. and they execute as a unit.

 

now I am not saying coding a snippet in the main body is always the same as a snippet in a function. The code is structured differently, so the behavior and effect will be different. but the difference is not due to delay in "calling" a function.

 

 

ps. "cross" is a built-in keyword, not a function.

Edited March 27, 2011 by Tams

[statsign 10]

I do understand, but I think this is good to have post on.

I'm not the best writer for sure.

When I say call the function, it is because it isn't inline and code has to move to the pointer for it. Certainly today, the delay for that is giga, but on ES ticks with 8000 lines? (rhetorical)

I understand what you mean - keyword, so I explain myself, boolean call to math to boolean - wrapped in a keyword.

Anyways, speed is king and if auto daytrading definitely go for overkill on processor speed and memory and internet speed.