I modified this to add ID as part of the label names. There were other problems that will occur as mentioned in comments. I have been through this before with other indicators and EAs not properly removing their own objects and removing objects ...

I'm seeking a trailing stop EA that surely must exist, any ideas?

Remember that version 6-15-10 has most of my new code removed. Fixed bug from version 6-09-10d in this version last week but not yet posted. The Timeframe parameter was in the wrong place. This version also shows expected spread and current actual ...

Indicators development for T101's not very simple method

Don, For some reason Quote is cutting the prior message so I am just pasting here to answer questions. // The following is needed to save as global variable #define NONE 0 #define BUY_ALL 1 #define SELL_ALL 2 I honestly am lost on why this is ...

Indicators development for T101's not very simple method

Not true. The BTR is the sum of the MA's from all 14 pairs with the yen crosses normalized by dividing by 100 to single digit values and 4 decimal places. Robert

Indicators development for T101's not very simple method

My reason for joining this thread was to help in removing bugs to the original EA and adding possible fixes to problems mentioned. It appears I have done too much. I took out almost all the additional code that I added. I only left the saving of ...

Indicators development for T101's not very simple method

I added some code to the init function that shows the trade type to be taken for each pair based on current direction of EMA(14) with result printed to the expert log. While not perfect it does show a possible filter. The idea is to try to trade ...

Indicators development for T101's not very simple method

BI_T101 crosses is not used by the current EA. It only checks red above blue or blue above red. There is no check for a fresh cross. The same is true for any trend check using TrendMagic, SuperTrend or LSMA. There is no check for a new trend change, ...

Indicators development for T101's not very simple method

I found some code in the EA to use spread. The problem is that using MarketInfo will only return the default spread, not the current spread. Current spread would need to use Ask - Bid for each pair. What is UseSpread suppose to do here? Robert

Indicators development for T101's not very simple method

V1.5 only used the IBFX pairs for the calculations of the lines. V1.6 allows for IBFX or other broker pairs. When I first followed the original thread FXDD did not have the same pairs as IBFX so I coded versions of the EA to use either set. The same ...

Indicators development for T101's not very simple method

I was thinking about finding a better lock profit with exit signal when the trend changes. If SuperTrend does not repaint then the buy trade from earlier would still be in play until SuperTrend reverses. The same appears to be true for Trend Magic. ...

Indicators development for T101's not very simple method

The current rules must all line up on the same bar. If the first rule is met but later is not met then the rules are all checked again from rule 1. Current rule check order Rule 1 is for Trend Direction. Rule 2 is Macd Rule 3 is BI_Red or BI_Blue ...

Indicators development for T101's not very simple method

Method 1 if(BI_Red > BI_Blue) BuyCondition3 = True; However, I think it is better to be: Method 2 delta_BI_red = BI_red(0) - BI_red(1); delta_BI_Blue = BI_Blue(0) - BI_Blue(1); (delta_BI_Red>delta_BA_Blue && delta_BA_Blue>0) in fact, this way is ...

Indicators development for T101's not very simple method

These input defaults, 40 stoploss and 10 RiskPercent, are in the next version. I also coded the Global saving in case of disconnect. That way there will not be bug reports of something not working for Profit Lock after a disconnect. I will post the ...

Indicators development for T101's not very simple method

mas toro, The code change you made will not work. BI_Red = iCustom(myPair+Pair_Suffix,0,"BI_T101_OTR_V1_5",UseIBFXPairs,10,5,288,0.0,0.0,"Che ck_Candle : 0 for current , 1 for last closed candle",0,true," 0 for S_R , 1 for Fast/Slow ...

Indicators development for T101's not very simple method

There is one more potential bug that is easy to fix. When there is a disconnect from the trade server for any reason an EA will re-run the init function. This will cause all variables to reset. If there has been a profit lock and the profit retraces ...

Indicators development for T101's not very simple method

I though I had already done that change. The new code does just that, checks AllPos for trades by this EA for closing. I will now only focus on fixing bugs only. One current know bug is for the profit lock code. A possible fix is to modify the ...

Indicators development for T101's not very simple method

Using GetOrdersTotal here would cause a problem if another trade is open by a different EA or manually. It would cause some of the trades open by this EA to be missed in the profit calculation. I might have missed a letter somewhere in the versions ...

Indicators development for T101's not very simple method

My reason for changing from i to 0 was to enforce to fifo rule. The first order places must be the first order closed. However, changing this back to i should still work OK because the fifo rule will be met unless another trade is open for the same ...

Indicators development for T101's not very simple method

Set the input for UseDonsMM to false. That will cause the EA to use whatever value is entered for nMMLots. Robert

Indicators development for T101's not very simple method

Since some of you are discussing trend I would like to share what I use. LSMA 25 has worked well for me and has less lag than sma or cci which is used in both of the trend indicators used by the EA at present. LSMA indicator is attached. If added to ...

Indicators development for T101's not very simple method