How-to-create-custom-BarHistory-and-plot-it-with-PlotBarHistoryStyle

Thank you Eugene!
That works!

Any ideas on these:
> Also for the PlotBarHistoryStyle - how do I plot up bars and down bars with different colors? The API shows only one option for color.
> What are valid values for "styleName" in PlotBarHistoryStyle (probably a list of valid values should be added to the documentation).

You can use the ChartStyleFactory.ChartStyles to get a list of installed chart styles, each such ChartStyle instance has a Name property.

We’ll have to add an override to allow you to plot up and down bar colors.

I was exploring on Visual Studio to try to understand why

CODE:
extBarsScaled.Open = extBars.Open * scaleFactor;

doesn't work because I thought it would.

So the extBarsScaled.Open TimeSeries is "get" but not "set". Perhaps it would be nice to make TimeSeries.Open, .Close, .High, and .Low settable too so the solution in the original post works? This would be more efficient because the .Add operation has to add more storage individually for each .Add executed.

The fancy solution would be to wrap the solution in the original post into a BarHistory constructor and allow that constructor (via "protected" set) to perform the TimeSeries set operation. But that's more development work. :(

I doubt it's a good idea to make these properties settable.

QUOTE:
I doubt it's a good idea to make these properties settable.

I tend to agree (And you knew I would.) because that can create "side effects" when foreign code monkeys around with class-library objects (WL objects). The problem is these introduced side effects aren't realized until 1000s of execution lines later, which means you need to lint the source code to find out what foreign code is corrupting things. (And I doubt the WL user with a 166-thousand line strategy has a C# lint utility.)

Adding a new BarHistory constructor is the safer solution, but that may have to wait until WL 7.1. :(

BTW, I experimented with setting float.NaN to price bars and that actually helped me with the following solution for plotting custom bar history with two colors:

CODE:

                        BarHistory SPXScaledUp = new BarHistory(SPX);
         BarHistory SPXScaledDown = new BarHistory(SPX);
         for (int i = 0; i < SPX.Count; i++)
            {
            if (SPX.Close[i] >= SPX.Open[i])
            {
               SPXScaledUp.Add(SPX.DateTimes[i],
                           SPX.Open[i] * factor,
                           SPX.High[i] * factor,
                           SPX.Low[i] * factor,
                           SPX.Close[i] * factor,
                           SPX.Volume[i]);
               SPXScaledDown.Add(SPX.DateTimes[i], float.NaN, float.NaN, float.NaN, float.NaN, float.NaN);
            }
            else
                {
               SPXScaledUp.Add(SPX.DateTimes[i], float.NaN, float.NaN, float.NaN, float.NaN, float.NaN);
               SPXScaledDown.Add(SPX.DateTimes[i],
                           SPX.Open[i] * factor,
                           SPX.High[i] * factor,
                           SPX.Low[i] * factor,
                           SPX.Close[i] * factor,
                           SPX.Volume[i]);

            }
         }
         PlotBarHistoryStyle(SPXScaledUp, "Price", "bars", this.settings.upColor, false);
         PlotBarHistoryStyle(SPXScaledDown, "Price", "bars", this.settings.downColor, false);

Thanks for adding "stacking" to bar annotations in Build 6. I can already see it the chart.

My next question - how do I add annotations to the secondary bar history?
I think secondary, or tertiary bar histories should have all the charting capability as the primary ones. My primary bar is already too crowded and will like to move some annotations (which belongs to the secondary one) to the secondary one.

I "think" the BarHistory constructor already sets Open, Close, etc. to Double.NaN by default, so you don't need to do that yourself. Just use .Add to set what's not a Double.NaN.

Also, Float.NaN is for single precision, and WL is using double precision. So you want to set undefined data to Double.NaN instead.

Now "some" compilers have switch settings that can change Float from single to double precision with the right switch setting. You'll need to research the C# switch settings for more information about that.