[Tams]

yes, you need to make it an indicator.

1. copy the code into your editor,
2. compile
3. after successful compilation, insert the indicator into your chart.

[Fredd]

Originally Posted by Tams »

yes, you need to make it an indicator.

1. copy the code into your editor,
2. compile
3. after successful compilation, insert the indicator into your chart.

Hi,

I tried to compile your zigzag, but it gave a syntax error at this line:

SwingTime(time_s)

Error message: Word not recognized by EasyLanguage

Unfortunately I am not an EasyLanguage expert, could someone compile it into an indicator? Thanks in advance.

[Tams]

Originally Posted by Fredd »

Hi,
I tried to compile your zigzag, but it gave a syntax error at this line:
SwingTime(time_s)
Error message: Word not recognized by EasyLanguage
Unfortunately I am not an EasyLanguage expert, could someone compile it into an indicator? Thanks in advance.

What program are you using?

SwingTime is a declared variable. It should not give you problem.

That leaves only time_s. But this is a reserved word, i.e. the word is built into TradeStation and MultiCharts.

[Tams]

Originally Posted by Fredd »

Hi,
I tried to compile your zigzag, but it gave a syntax error at this line:
SwingTime(time_s)
Error message: Word not recognized by EasyLanguage
Unfortunately I am not an EasyLanguage expert, could someone compile it into an indicator? Thanks in advance.

you can try this: replace time_s with a zero.

change
SwingTime(time_s) ;

to

SwingTime(0) ;
.

[Tams]

Originally Posted by daedalus »

Thanks for sharing. I particularly love the HH/LL indicator. So many new traders can't grasp this concept and to have it literally spelled out for them is a very powerful learning tool.
Kudos to you!

if you combine ZigZag with the HH/LL indicator...
the chart will give you a whole new vision.

;-)

[thrunner]

Originally Posted by Tams »

That leaves only time_s. But this is a reserved word, i.e. the word is built into TradeStation and MultiCharts.

Thank you for your contributions, Tam, and welcome to the forum.

Unfortunately, Tradestation (TS) does not have timing in seconds resolution and time_s is not a reserved word in TS EasyLanguage (EL). so you should preface a lot of your MC EL trendline code by noting that it may not be TS compatible.

For example, most of the functions with seconds resolution in MC, such as time_s, TL_SetEnd_s, TL_SetBegin_s etc need to be replaced with their equivalent TS versions such as: time, TL_SetEnd, TL_SetBegin.

Another caveat is that MC can handle EL errors, especially trendline code errors, without throwing up exception as much as TS. What you will find is that TS will often not plot MC trendline codes at all and you have to debug the program completely when moving from MC to TS.

[Tams]

Originally Posted by thrunner »

Thank you for your contributions, Tam, and welcome to the forum.
Unfortunately, Tradestation (TS) does not have timing in seconds resolution and time_s is not a reserved word in TS EasyLanguage (EL). so you should preface a lot of your MC EL trendline code by noting that it may not be TS compatible.
For example, most of the functions with seconds resolution in MC, such as time_s, TL_SetEnd_s, TL_SetBegin_s etc need to be replaced with their equivalent TS versions such as: time, TL_SetEnd, TL_SetBegin.
Another caveat is that MC can handle EL errors, especially trendline code errors, without throwing up exception as much as TS. What you will find is that TS will often not plot MC trendline codes at all and you have to debug the program completely when moving from MC to TS.

Thanks for the heads up.
Somehow I always thought time_s is a standard reserved word in TradeStation.

In that case, I better make 2 versions of each code, if seconds are involved.

[Tams]

HL Bracket v2.2

This program marks the High and Low of n bars back.
Useful as a guide for stops, break outs, scalping, etc.

The number will reverse color when the price breaches the bracket.
.