Miro, if you'll convert this, make sure FST's namespace is used, it's no use in FSB.

This is the reason I choose this indicator to demonstrate the new parameters.
As I announced earlier, all new indicators are both compatible with FSB and FST. But that doesn't mean that there is no separation in functionality.

There is a new parameter: IsBacktester. This param is equal to true when the indicator works in FSB and false when works in FST.

You can see for an example: DateFilter
Date filter works only in FSB.
I'm using IsBacktester in constructor to set an warning message when indicator is started in FST.

if (IsBacktester)
   WarningMessage = "This indicator is designed to be used in the backtester only. It doesn't work in the trader.";

This warning will be visible only in FST. I cannot demonstrate that because Date Filter is internally banned in FST, but everyone can use this technique in other indicator.

Later, In Calculation method. I'm using:

if (IsBacktester)
{
    switch (IndParam.ListParam[0].Text)
    {
        case "Do not open positions after":
            for (int bar = firstBar; bar < Bars; bar++)
                if (Time[bar] < keyDate)
                    values[bar] = 1;
            break;
        ...
    }
}
else
{
    for (int bar = firstBar; bar < Bars; bar++)
        values[bar] = 1;
}

We see that the indicator calculates signals in FSB, but sets 1s for all bars in FST (Indicator confirms both direction trade).

I'll use same format but in opposite direction for Spread Limiter:
- It will be available for loading in both programs.
- It will gives reasonable signals in FST.
- It will warn that is not suitable for FSB (when loaded there)
- It will not have any effect on backtest in FSB.
- It will not be used from Generator. I'll set IsGeneratable = false; (also new param)

Why I want to use this format:
1. You never know what a user will do. It may put this indicator in FSB.
2. It will not prevent strategy written in FST with this indicator to be loaded in FSB.
3. We'll have one set of indicators for all programs.

This namespace is no longer used. We use the following namespaces for all indicators in all three programs.

using System;
using ForexStrategyBuilder.Infrastructure.Entities;
using ForexStrategyBuilder.Infrastructure.Enums;
using ForexStrategyBuilder.Infrastructure.Interfaces;

namespace ForexStrategyBuilder.Indicators.Store
{
    public class DateFilter : Indicator
    {
        ...
    }
}

Wow, Footon, you have been a great contributor to FSB and FST. Thanks muchly for all you have added.

Thank you, Dave! But couple of days ago you said you didn't saw my indi corner indis until recently, now you say you're seeing the spread limiter for the first time, what have you been up to, mate?

I come here from the Feature Request forum of FSB.
This indicator does not make sense for FSB since FSB uses constant Spread value for the whole data series, but I can convert it in the new indicators format for FST. I'll use it  to demonstrate some new indicator parameters.

I believe the request wasn't done for FSB (the requestor is advanced user of FSB and knows it can't be achieved in FSB) but for FST. This indicator in particular is for FST. FSB won't load the indi.

Indi reads this:

namespace Forex_Strategy_Trader

Miro, if you'll convert this, make sure FST's namespace is used, it's no use in FSB.

indi is not working. FSB doesnt see it

It is meant only for FST. It cannot be used with FSB, as in FSB spread is a constant value.

increases/decreases part is very tricky

The problem is that Spread is not a series of values. We have only one, current value.

for (int iBar = 1; iBar < Bars; iBar++)
    showspread[iBar] = spread / point;

The code above do not make it a series. It puts last Spread value in each cell of the array.

There is not  an easy way to compare Spread values. Even we cannot compare current spread with the previous bar one.

An indicator cannot hold an array with statistics about the spread. It will be reset many times because its constructor is called in various events.

It's possible only if FST or expert collects Spread stats and indicator has access to it.

Thank you!

I still do not understand why Spread declaration gives the context error, in the source it is declared as an instrument property next to others like Digits and Point, which both work very well.

Spread is not included in base class "Indicator" and you cannot access it directly as Digits and Point. You can use Data.InstrProperties.Spread instead.

You can use Point directly because it is declared in Indicator class:

protected static double Point { get { return Data.InstrProperties.Point; } }

I'll also add the Spread in next releases like that:

protected static double Spread{ get { return Data.InstrProperties.Spread; } }

You can use what is better for you:
Spread gives a number as 32;
Ask - Bid gives 0.00032.

Info panel updates on a new bar or when you move the mouse over the chart.

The info panel is really not updating, if chart is opened, then maybe 2-3 times with the incoming ticks the spread changes and then it freezes, if tabs are toggled and chart is brought back for viewing, info panel updates. It might not be a huge problem when internally it's always up to speed to the current spread, so am I right in assuming that the indi has always the latest spread value, even though it doesn't update it in the info panel?

I still do not understand why Spread declaration gives the context error, in the source it is declared as an instrument property next to others like Digits and Point, which both work very well.

double bid = Data.Bid;
double ask = Data.Ask;

// Calculation
double spread = ask - bid;
int firstBar = 1;

// Calculation of the logic
double[] spreads = new double[Bars];
for (int bar = firstBar; bar < Bars; bar++)
     spreads[bar] = spread;

Prototype is attached below.

Note: Info panel is not updated at every tick I think, but spread must be correct.