Mike Medved

In MT, to add a symbol, you simply start typing it. Somehow one of your keyboard keys thinks it is getting pressed (and stuck).

Yeah, the problem with those patterns is that their definitions are very vague and hard to define in exact terms. What one could do I guess is take the last few (4? 5?) local minima and maxima (which also means you have to define what local minimum/maximum is), run linear regression lines through both sets, and then check that 1. the points on which they are constructed lie close (again, "close" has to be defined) to the lines and 2. they intersect in the future and 3. the slope of the top one is a lot less (1/10th?) than the slope of the bottom one? How does that sound?

Question: are the drawings completely arbitrary - that is, there is no set relationship between the up line and down line, the user can just put the dots of the drawing wherever he wants? Basically, is all you want a multiline-drawing tool?

Note how on the second pic of yours the "jaggies" in the lines are not there.

With AMTD, it is better to backfill "continuous" contracts - for example @ES.

Fixed - go to Dashboard's File menu / Help / Check for Updates

Jason, the problem is the lexical parser we're using does not give the right column for the error sometimes. Correct row though

There are three ways to specify a color. 1. Color.something - like Color.Black, Color.White, Color.Lime etc. - these are absolute colors. 2. SysColor.something - like SysColor.Positive, SysColor.Bid, SysColor.MainIndicator1 - these colors are taken from the current chart's color scheme. 3. the hex format. 0xFF9399FF - the first FF is transparency, just always leave it FF. 93 is the red component, 99 is green, FF is blue. So this color would be a bluish gray. FF is max, so the 0xFF9399FF is a lightish blue. See https://www.color-hex.com/ your 0xFF9399FF would be equivalent to #9399FF there.

Also - in order to scan using several paintbars, you have to combine the several paintbars' code into one scan, and set the scan results or scan result colors differently for the different code's triggers. Only one scan can run on a portfolio at a time.

Scanning is pretty efficient. Past the initial setting up of the scan, as the data comes in, the scan calculation is done only for the last candle. The "problem" with scans is that each symbol has to, initially, recalculate a bit of candle data for itself (how much candle data depends on the indicators in the scan) and keep those candles and the indicator values around while it is running, thus using up some memory. But I know some MT users are running 1500 symbol RT scans with some quite complex code in them and MT seems to handle it ok. Modern computers are pretty amazing in terms of performance. I started programming in the 70s. Computers changed quite a bit during the last 40 years or so. And yes, same code can be used for scans and paintbars. We deliberately made it that way.

The PB's SetColorAndShape sets, unsurprisingly, the color and shape at the particular candle. Where to place that color and shape is not decided at the code level (unless you do SetYValue). At the time you place the paintbar on the chart, in its parameters, you specify where you want that paintbar to appear.

That's the personal service for the complainers. What I meant is it has been fixed and will be pushed out in the next release.

Will be fixed.

This will work in the beta after the new production that is about to be released.

If you want to overlay and compare two paintbar lines and want to adjust scales, do it in an extra chart (above or below the main one). You can link two indicators to show on the same chart. The linked indicators are usually scaled so that they overlay each other. To do that, if the scales are similar, they do not change, but if they are dissimilar, they are adjusted.

Sorry we missed this post and never answered it. Question: does this happen right away when you run a scan or a long time after the scan starts? Is it some particular scan that causes it? If so, can you export it and send it to us to support email?

TDA is doing a server update for the calculated indexes and it'll be released soon. (Soon = week+).

LOL

Well then it should be @BRRU19 in MT as well no? I tried that and it works.

hm. Ok how do you enter it in TWS? I type in BTC, and it gives me no futures option. Same with "Bitcoin"?

Not sure... I cannot easily check since my acct is not enabled for BTC futures right now.

what about @BTCU19 ?

Are you using TDA as the source? I just tried and it is working/updating on the portfolio.

I notified TDA API guys that it is not sending data on $ISSU

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.