Actually, we have so many choices of indicators that additional ones are not really required. There are only a couple primary purposes for indicators like trend and range and volatility....... and I am sure those are adequately covered with the present inventory.

By adding indicators, we reduce processing time and complex what we are trying to do.

The generator explores all possibilities of the math on a random basis....... there are literally thousands of calculation patterns, maybe millions, available for the generator....... considering that each indicator has five or seven variables.

My current interest in indicators is to reduce the number of iterations to get to the good news quicker.

I haven't seen Footon recently, in fact it doesn't seem there have been any new indicators in quite awhile.

A couple people have learned a lot about the indicators...... Footon is one of those......, myself, I am just hoping you keep asking questions. lol

- FSB Pro calculates the indicators only once for the complete DataSet. Depending on the indicator's role it uses different "components" of type IndComponentType  to save the output values. The IndicatorComponent has a value array. It is with the length of the DataSet. The "value" have one value of type "double" for each bar.

Value of 0 means no entry/ exit price or entry/exit signal.

   - IndComponentType.OpenLongPrice - the component.value stores the entry price for a long position. It has one entry price for a bar. It can be bar Open for indicators as "Bar opening" or other value for indicators as "Moving Average" or "Pivot Point"
   - IndComponentType.OpenShortPrice - stores an entry price for short positions.
   - .OpenPrice - entry price for both long and short entries. This can be used for indicators that have a single entry price (Moving Average, Bar Opening...)
   - .CloseLongPrice, .CloseShortPrice, .ClosePrice - are the same as above but FSB checks them for closing.

   - .OpenClosePrice - here you can set a single value that will work for both entry and exit in both directions. (for example Moving Average)

  - .IndicatorValue - you use this type to store a value that you want to show in the chart or in the dynamic info, but it doesn't affect the trading. For example, the middle line of Bollinger Bands.

- .AllowOpenLong, .AllowOpenShort - you set 0 or 1 for these types. FSB uses them to check if long or short entry is allowed for the bar.

- .ForceCloseLong, .ForceCloseShort, .ForceClose the same as above but for "allowing" closing signals.

EDIT - ok I think I understand now. I'm so used to metatrader and trading station coding/backtesting.

I see since the data set is loaded in advance, I need to create my own loop to represent the current bar,
as in for (int bar = 0;bar < Bars; bar++)
then bar is the current bar for the calculations.

how many indicators do I have to create to get a free copy haha
I am running out of computers to run the demo

Yes, FSB Pro is an excellent excuse to buy one more every two weeks

I'll give you an idea:

When the Trial expires, FSB Pro doesn't want to save strategies...
However it happily saves collections.

haha yeah, I don't think my wife would go along with that, but I agree it's a great excuse

thanks that's good to know!

you create a new IndicatorComp, and set the type to IndComponentType.AllowOpenLong. 
Then when that value is a 1 it will open a trade? Is that right?

Yes, this is correct.

We set "1" where the indicator allows an entry and "0" where no entry is allowed.

Thanks for all the help Mr Popov, does that just mean whether long trade and short trades are allowed or is that the actual signal to buy/sell? I don't see anything else that looks like a buy/sell signal.

also I take it we cannot reference the ask or bid price separately, I assume it's always the ask price?

how many indicators do I have to create to get a free copy haha
I am running out of computers to run the demo

Yes, FSB Pro is an excellent excuse to buy one more every two weeks

I'll give you an idea:

When the Trial expires, FSB Pro doesn't want to save strategies...
However it happily saves collections.

also do the trades open on tick data (intrabar) or bar open? Is that decided by the indicator or FSB?

You can safely pretend that all calculations are executed on "tick" data. Actually there is no such thing, but the backtetsing engine cleverly puts a tick at the point of the execution. It is more "ticky" than the MetaTrader's "every tick" mode.

you create a new IndicatorComp, and set the type to IndComponentType.AllowOpenLong. 
Then when that value is a 1 it will open a trade? Is that right?

Yes, this is correct.

We set "1" where the indicator allows an entry and "0" where no entry is allowed.

is there a way to draw an indicator into the future?

No, we cannot. The indicator uses the data series provided to it from the strategy.
You can "delay" the signals by using "shift" as in Moving Average:

 protected double[] MovingAverage(int period, int shift, MAMethod maMethod, double[] source)

But the shift cannot be negative. This limitation is done to provide equal behaviour in the tests and in the trading. Obviously we cannot see an indicator form the future in live trading, so we have not to use it for backtesting.

Is the current bar 0 or 62777?

We give the data series to the indicator via the Calculate method.

So, we can use the price directly with Close[Bars-1].

ok awesome that's what I thought, thanks Mr Popov!

p.s. how many indicators do I have to create to get a free copy haha

I am running out of computers to run the demo

By 'also is there a way to draw an indicator into the future?' do you mean on the indicator chart in FSBPro..?

Ichimoku extends into the future but does not show that extension on the indicator chart.

Hi Blaiserboy, yes that's what I meant. I wonder if we can trick it by subtracting a certain number from the current bar, which I think I figured out now isn't 0 but is the large number like 62777.

Oh well, doesn't matter. I don't think people use fsb to look at the charts as much as for the strategies anyway.

Can you answer any of my other questions by any chance? Oh nvm, I see Mr Popov just replied

Is the current bar 0 or 62777?

We give the data series to the indicator via the Calculate method.

public override void Calculate(IDataSet dataSet)
        {
            DataSet = dataSet;

and can use is later view the DataSet class together with all market settings.

The oldest bar in Data is 0. Te newest bar is Bars-1
Example.
Oldest close is DataSet.Close[0]
Newest (or current if no OOS) DataSet .Close[Bars-1]

The, DataSet is defined in the base Indicator class where we have also "shortcuts" like:

        /// <summary>
        ///     Bar highest price
        /// </summary>
        protected double[] High
        {
            get { return DataSet.High; }
        }

        /// <summary>
        ///     Bar lowest price
        /// </summary>
        protected double[] Low
        {
            get { return DataSet.Low; }
        }

        /// <summary>
        ///     Bar closing price
        /// </summary>
        protected double[] Close
        {
            get { return DataSet.Close; }
        }

So, we can use the price directly with Close[Bars-1].