Script{} definition error

[mark.917]

ThinkScript Drives Me Crazy
Why is it that the compiler does not complain about top1 and bot1 but it complains about st?

 

[ApeX Predator]

Post the whole code. It will be easy to debug.

 

[armybender]

Only thought is that st is not recursive, so it doesn't need a DEF above in advance of the variable assignment.

Try putting DEF inside your first set of curly braces.

 

[mark.917]

Thanks to both of you. I blew away the code and started over. Not sure what is different from the first time other than there must have been some type of syntax error somewhere else in the code.

I did try the DEF inside the conditional statement and IIRC, it said that was not allowed.

I also find it disappointing that ThinkScript will now allow plot statements, AddVertical, AddCloud, etc as part of conditional statements.

 

[halcyonguy]

ThinkScript Drives Me Crazy
Why is it that the compiler does not complain about top1 and bot1 but it complains about st?

View attachment 19536

next time post whole code.
was probably a missing st = ... line after those lines.
thinkscript is horrible about highlighting errors. usually the problem is after the red highlights.

 

[MerryDay]

I also find it disappointing that ThinkScript will not allow plot statements, AddVertical, AddCloud, etc as part of conditional statements.

Think of it this way.
The Condition Widget is uniform across watchlists, scans, conditional orders, etc...

The formatting statements such as plot statements, AddVertical, AddCloud can't be used in any of the other modules.
That is why the Condition Wizard requires all conditions be defined before formatting.

This way all the logic is interchangeable throughout all modules.
After that, the unique simple straight-forward formatting statements can be appended when the condition script is used for displaying on a chart.

 

[mark.917]

next time post whole code.
was probably a missing st = ... line after those lines.
thinkscript is horrible about highlighting errors. usually the problem is after the red highlights.

Good to know. Thank you halcyonguy you're always very helpful.

 

[mark.917]

Think of it this way.
The Condition Widget is uniform across watchlists, scans, conditional orders, etc...

The formatting statements such as plot statements, AddVertical, AddCloud can't be used in any of the other modules.
That is why the Condition Wizard requires all conditions be defined before formatting.

This way all the logic is interchangeable throughout all modules.
After that, the unique simple straight-forward formatting statements can be appended when the condition script is used for displaying on a chart.

You know, I've tried to access that wizard but it is always grayed out.

My background is C++, EasyLanguage, MQL4 and a little Pine Script and so far ThinkScript just hasn't impressed. Even the editor is lacking and buggy (try to arrow quickly to a piece of code and it jumps to line 1). Once I get more experience maybe my opinion will change. I hate asking for help and trust me I try to solve things on my own before posting but I do appreciate the community here and their willingness to help.

 

[ApeX Predator]

Thanks to both of you. I blew away the code and started over. Not sure what is different from the first time other than there must have been some type of syntax error somewhere else in the code.

I did try the DEF inside the conditional statement and IIRC, it said that was not allowed.

I also find it disappointing that ThinkScript will now allow plot statements, AddVertical, AddCloud, etc as part of conditional statements.

You can define conditions on the plot statement itself, like every scripting language, TOS scripting has its limitations.

 

[mark.917]

You can define conditions on the plot statement itself, like every scripting language, TOS scripting has its limitations.

Sure thing. Still learning so I'm sure all of it is on me.

 

[halcyonguy]

You know, I've tried to access that wizard but it is always grayed out.

My background is C++, EasyLanguage, MQL4 and a little Pine Script and so far ThinkScript just hasn't impressed. Even the editor is lacking and buggy (try to arrow quickly to a piece of code and it jumps to line 1). Once I get more experience maybe my opinion will change. I hate asking for help and trust me I try to solve things on my own before posting but I do appreciate the community here and their willingness to help.

don't ever feel bad for asking questions. ask all the questions you can come up with. many great people here willing to help.
i see that cursor jumping to line 1 too, drives me bonkers.

-------------------

guessing you haven't studied these yet.
save the following info for a future day, info on fold and script
https://usethinkscript.com/threads/simple-explanation-of-fold-trying-to-learn.8044/#post-76663

fold (looping)
https://tlc.thinkorswim.com/center/reference/thinkScript/Reserved-Words/fold

script (sub routine)
https://tlc.thinkorswim.com/center/reference/thinkScript/Reserved-Words/script

 

[Joshua]

Variable assignment is obligatory in all cases. That error means that you've failed to assign a value to St in one or more logical branches. At minimum, you would have to assign Double.NaN to St in the Else clauses.