Mike Medved

You're right, I forgot the public part. And setting it to 999999 would be in PaintbarClearState - but it only affects the candles from the beginning of the chart to the first occurrence of your condition - basically if you don't set it that way, it will assume that the candle right before the beginning of the chart satisfied the condition. As you can see, having C# available to program paintbars/scans is very versatile. Hope the help file clarified things.

There is an option in the ribbon menu to add State to the indicator. That adds a bunch of code, including the CurrentState and a few state-initializing, saving and restoring functions. You put the Boom into the PaintbarState definition: .fctbNone{ color:#000000; } .fctbStyle8{ color:#808080; } .fctbStyle2{ color:#008000; } .fctbStyle5{ color:#0000ff; }/// <summary> /// Holds paintbar state - fill with variables needed to be preserved for next paintbar calc /// </summary> private struct PaintbarState { int Boom; // <--- this is what you add } see https://www.medvedtrader.com/trader/WebHelp/state_keeping.htm I really worked on that help file to make it as comprehensive as possible

Well, the way to do this would be - have a state variable, let's call it Boom (as in "something happened"). Set it to 9999999 or something to begin with. Any time an event happens (like "Outside bar (engulfing)") - set CurrentState.Boom to 0. If the event did NOT happen, do CurrentState.Boom++ This way you can check the CurrentState.Boom to see how far back the event happened.

To tell you the truth, I never liked it It wasn't a true ticker tape (which I believe shows block trades as they happen?). I guess we could make one that would actually do that (show trades as they happen) but I am not sure what criteria to apply (that is, which trades to show). Also, during high volume times it probably would go way too fast?

This is tough to do. Basically, those patterns look great in pictures, but when you look at that stuff in real life... The lines are never exactly parallel, the local minima/maxima are never exactly the same, etc. I will look into it. Candle patterns are a lot easier because they really only work on maximum 5-6 candles. The chart patterns can be quite big - 30-40 candles, right? It would help if there was some word descriptions of those. Like let's say ascending triangle = "local maximum followed by local minimum followed by a local maximum that's approximately the same as first followed by local minimum that's significantly higher than previous one, followed by a move significantly above the maxima" - would that be an accurate description?

When you export, select the "User Settings" checkbox.

Yes. Fixing.

If you missed it, I'd like to point to our convenient looping functions in Advanced code: https://www.medvedtrader.com/trader/WebHelp/index.html?advanced_looping_functions.htm From our support emails, it seems that paintbar users may not be aware of them. For example, if you have a variable SMA20 which is an SMA and you want to do something if it has been rising for the last 4 candles, all you have to do is call: All(4, SMA20 > SMA20[1]) // will return true for that condition. Don't have to use a for loop etc. or you want to check if the Close was above SMA20 in at least 5 out of 6 last candles... Count(6, Close>SMA20) >= 5 nice and simple.

Wow, 5.5 years

When you say "Take last SIZE" - where is that last size coming from? If that is from the Last Size column in the portfolio, that's the last trade's size. Which means that the volume increase would be only for the last trade. That's not what you want. When you say "Size last X minutes" - without going back and looking at past data, how exactly can we get that?

In order to know the volume increase you have to know either what the cumulative volume was X minutes ago, or to have a running queue of all ticks for the last X minutes and add up those volumes. Either way, that's a "chart" kind of thing, and not just simple L1 data. That's what Jerry meant by "requires chart/paintbar machinery to compute".

Note that although there is only one scan per portfolio, it can include as many different criteria as you want and concatenate the results in the ScanResult string...

Since Poloniex does not do USD, it would be #BTC.USDC

You can do all kinds of customization in the message. When you open the notifications dialog, there is a second tab there called "Note". Switch to that, make it something other than "Not Change" and right-click to insert all kinds of info about the symbol, its price etc. [DESC] will contain the original alert note passed from the alert itself.

MOber, the point of you giving the alert a name is so that you can set up notifications for that alert later. When you place the paintbar (or any other indicator) on the chart, you can edit its parameters by clicking on its legend in the chart. Once the parameter popup opens for the paintbar, you will see the Alert you set up. You can turn it on/off or set up its notification options there.