Pine Script debug PRINT LOGS are finally here!

[@TheArtOfTrading]

🔷 TradingView Blog Post: www.tradingview.com/blog/en/pine-logs-in-pine-script-40490/?offer_id=10&aff_id=15271 🔷 Debugging Lesson - Part 1: kzbin.info/www/bejne/mGSzkomQoKmVeqs 🔷 Debugging Lesson - Part 2: kzbin.info/www/bejne/ZpmnhYx5mZKoadk

[@XDosShane]

I've been using labels to this lol. This is going to be super useful

[@luisnannini]

Lol cant believe they took so long, got everybody debugging in the dark

[@TienTran-dn3jl]

Thanks for new things update! This feature from Tradingview is shined.

[@Alphaa101]

Great! Waiting for your video about more advanced RSI divergence.

[@brianmcelhenny7645]

Oh man! This is gonna be so helpful. It was still cool to learn your debugging techniques with the label and such... but yea, this will be so much better! 😎

[@marcelokage]

Long time waiting for that... Thanks Universe!

[@ernestosabado5712]

Thanks a lot, this is very usefull!! i tried to log the volume (from a very common indicator), but wasn't able to grab its data. please would you tell me how to work with? Best regards

[@ezrakoper]

Any filter option to show only info, warning, or errors

[@gregkendall3559]

I wish there was a way to export the log. I really need that.

[@reylopez5337]

Great video brother. Is it possible to put a live pip counter on trades that are open on a strategy? whether they are buy or sell on forex. i have a EX4 attachment that counts Pips on any trades that I am in but it only works on MT4 . thanks in advance. ANYONE??

[@hu5116]

OK, I'm assuming a Pine Scripter from TV is going to see this: FEEDBACK: 1) My comments on nomenclature below still hold: say what you mean and mean what you say - this is not a log, although I suspect you all were thinking that way because YOU guys at TV may be logging data from your runtime to produce this. Fine, but that is not OUR interface or use of it. So those comments still stand (see my prior comment on this vid). 2) YES, this is fantastic! But only within the context that every other program language since Assembler has had a Debugger of some kind! This is not a Debugger, so you still have a ways to go. But this certainly is infinitely better than before (since it was zero before, anything is infinitely greater!). 3) there is a nice locator symbol button to the upper right of each log entry to take you to the associated Bar: great, but I have found myself usually wanting to go from a Bar (where I see aberrant indicator behavior) back to the corresponding log entry. I understand why you might have done this first (easier) but we need to be able to go from Bar to log entry. 4) You use "T" to delimit the date from the Time in each log entry title, but with all those digits, its hard to see. Recommend deleting that "T" and just leave a space: we can figure out its time thereafter. 5) The documentation needs to explicitly and comprehensively document all the formatting structures and symbols you accept and use. The current doc is not formally structured to give this, and is incomplete, for both the log call and the format call the doc refers one to. Yeah I was able to figure it out, but its not explained and I dont know what other formatting options I might have available to me. 6) An important one, often times a biggest issue is trying to get your indicator to indicate: that is, maybe you missed using an nz or something like that so the indicator cant get started correctly. Therefore, one of the biggest uses of log is going to be at the start of a security time series: I use COINBASE because it has not been around long and you can actually get to the beginning of the series. But that also means needing to go to the beginning of the Log to see that beginning of the series results. There needs to be a "Popup to Top" button, maybe in the title area above the Log panel to pop the Log listing up to the first one: its a pain to have to scroll, scroll, scroll to get there. 7) If I click on a Log entry, its needs to highlight (it sort of does now, but poorly so you can hardly see it) and then too is needs to STAY highlighted if and when I scroll the listing up and down (usually looking for what happened before or after). 8) Back to my critique of calling these logs by three separate titles with no rhyme or reason why they should be called that, (the error records no errors, the warning not warnings and the info no info), just give us a text field to fill in with our own label. Maybe there is a default of "Log Entry" or some such (although like stated before, this is NOT a Log!, call it just "Output"), and then let us change it to a meaningful label for its place in our code. If you want to limit us to 3 that is fine. That would be MUCH clearer and more acceptable than use the artificial and meaningless labels of "error", "warning", and "info" that you have forced us to use. There is likely a few other issues I could address, but fix these and we'll see if more needed. BTW and FWIW, having used this Log feature now for just a little bit, I ABSOLUTELY do Love it! Kinda like a starving poor person really appreciates even just a small bowl of rice. So with hat in hand, THANK YOU for implementing this (if but Finally!)

[@kevinstowell6531]

yes, sooooo overdue!

[@output250]

Bro Can you make indicator (shooting star)

[@ProgressiveEconomicsSupporter]

An unusual dream came true 😎🇩🇪

[@hu5116]

I'll watch it again, but at the end this is again an arcane misdesigned bungle by Pine Script. This is NOT a LOG! A log is a FILE that is recorded in the background saving typically mundane uneditable details of the processing going on in a main program or processor. What this IS is an output screen, suitable synonyms for which are Output "display", "terminal", "monitor", "screen" 'dialog", "panel" and maybe others, but NOT LOG! Second, why are there three types? Why are these three types named warning, error, info? I did not perceive that if Pine Script has an error, that it will use an error type of log, correct? I mean the error log does not COME from a Pine Script error, right? The warning log does not come from a warning generated from inside Pine Script, right? The info log does not come from Pinescript generating some informational message to share, correct? If it does, this was not at all clear. If not, then this is an example of superfluous complexity for no reason. I am thinking that these are just 3 different display message types to be used by the user for maybe sorting things? If so, then why not just include a "Message Type" parameter in the call syntax, and then the user can have an infinite number of different message labels that they can sort on to their hearts content! Maybe I misunderstood this whole thing (I'll rerun the video) but if not, then this is the kind of dumb ass design details that mar such an otherwise potentially wonderful platform and that just irritates the snot out of me! (Sorry). Oh BTW, I'm VERY appreciative of the video (just in case that might not have come across in my critique of the Pine Scrip malaise in language design). THANK YOU VERY MUCH!

[@TIFAxYUI]

我也想玩！