Adding permanent notes to default/locked studies and tickers

[c0der]

1. E.g. I want to put a short note to remind myself what Stochastic means within the study itself. However, I can't edit the script to add in chart labels/bubbles. I also don't want to put it in thinklog notes as it will be an extra step. Is there an alternative way?

2. I want to store long paragraphs of text (E.g. investment thesis) on the ticker chart (again, not in thinklog notes), AND without it moving away as the chart progresses to the right. any way to do this?

 

[MerryDay]

You can put TOS indicators into a custom study and then add your notes, labels, bubbles, etc...
To here is a neat trick to find the syntax to reference TOS indicators:
https://usethinkscript.com/threads/reference-syntax-and-indicator-settings-in-thinkorswim.5022/

 

[halcyonguy]

1. i think this is what merryday was saying, copy the original TD code and paste into a new study. then you can change anything you want.

another option is to add a hint to the study or a variable.

2. don't complicate things. put your notes in text files and view them as needed. name them yy-mm-dd-symbol
or symbol-yy-mm-dd , whichever makes sense to you.

https://tlc.thinkorswim.com/center/...pendices/Appendix-C---Customizing-Study-Hints

 

[halcyonguy]

if you think saving notes in external file may work for you, here are a couple ideas.

a couple of android apps i use, for writing notes, programming snippets, saving links. i like them enough that i bought the full versions.

my notes
https://play.google.com/store/apps/details?id=net.kreosoft.android.mynotes

diary , diaro
https://play.google.com/store/apps/details?id=com.pixelcrater.Diaro

 

[rad14733]

@c0der Here is another spin on your idea... Considering how Thinkscript is a self-documenting scripting language, not a compiled language, any additional text within scripts uses up overhead and can essentially bog down processing of the script by the realtime parser... That is just one of the reasons why scripting languages should be written as self-documenting code rather than using short cryptic variable names - to keep things simple and relatively uncluttered... Moderate length variable names that are self-describing, yet not overly long, essentially negate the need for overly verbose comments within the script... Placing either a local path or URL to extended notes, as has been suggested, is a far better method...

 

[RickAns]

Never thought about that, thanks @rad14733 . As a learning code scripter I thought extra remarks or comments would be helpful with debugging workflow. Did not think it would slow the processing part down. Figured things behind the # were ignored. Good to know.

 

[rad14733]

Never thought about that, thanks @rad14733 . As a learning code scripter I thought extra remarks or comments would be helpful with debugging workflow. Did not think it would slow the processing part down. Figured things behind the # were ignored. Good to know.

I'm an old bit-fiddler from way back when every byte of code and processor clock cycle mattered and a lot of modern coders never had such concerns, yet it all still adds up in the end... Some comments are required but they should be concise, leaving the lions share of documentation up to the scripting itself... That's the beauty of scripting languages and Structured Query Languages (SQL)... Anyone who has coded in assembly language or other low level languages can attest to how cryptic they can be... I shudder to think of the volume of assembly language lines of code I wrote decades ago, amongst other lower level languages...