Can I stop code from working but still keep it in the code edit area?

[EddieM]

When in the code edit area can i add in something around some lines of code so it stays in the edit area but will not work to show up on the chart.

I tried adding a line and that wouldn't work.
So to disable ares of the code but it is still there so I can turn it back on or off as I am testing different things without removing it.

Thanks.

 

[rad14733]

@EddieM Yes, the best way to run TOS while editing scripts is to use a detached window of Tools > Thinkscript... You can have multiple Studies/Strategies open for editing and as soon as you click Save any Charts running that script will instantly update, reflecting your changes... Detach the Thinkscript panel before opening scripts for editing for best results... I sometimes have 4 - 6 scripts open for editing at a time and bounce between them and monitoring Charts... The image below is a detached panel with 3 scripts open for editing... The Save button won't appear in the upper right corner until you have made an edit to the code... Hope this helps...

 

[halcyonguy]

When in the code edit area can i add in something around some lines of code so it stays in the edit area but will not work to show up on the chart.

I tried adding a line and that wouldn't work.
So to disable ares of the code but it is still there so I can turn it back on or off as I am testing different things without removing it.

Thanks.

i use input to control test codes/labels/bubbles/...
you can do something like this, or add the variable to a plot formula, to control when it is seen.

input test1_label = no;
addlabel(test1_label, " test stuff", color.cyan);

 

[rad14733]

My first post, while good information, didn't address your request as I'm reading now...

Another potential solution would be to use the script structure if you are working with a larger block of code... Once you get the hang of them they can come in quite handy...

 

[mashume]

To "comment out" a line of code so that it doesn't do anything put a "#" before the line:

def price = close;
# def price = open;

This will not error out as price is NOT defined twice. The second one is a "comment" and is not parsed by the ThinkScript engine.

Perhaps that helps?