Sure. The 2 things I did was rename the indicator to a one word name. Instead of "Pipfinite Trend PRO MT5" I made it "TrendPro". Not sure if this was absolutely needed but I did it for ease anyway. The other thing and the more important thing is that when you're loading the custom indicator into Fx Dreema, DO NOT LOAD any inputs beyond the MAIN SETTINGS. If you do, you'll get the compilation errors. If you're using this indicator or any other Pipfinite indicator, you shouldn't need any inputs beyond the first few anyways. Also, when adding the Periods input, change the name to ThePeriods or whatever else other than just "Periods" as this affects this particular input in a negative way for some reason.
Latest posts made by Cgammons01
-
RE: Pifinite Trend Pro Compilation Errorposted in Questions & Answers
-
RE: Pifinite Trend Pro Compilation Errorposted in Questions & Answers
I have figured this out. Let me know if anyone needs help. Thanks!
-
Pifinite Trend Pro Compilation Errorposted in Questions & Answers
This question has been asked before on these forums by someone else but there wasn't an answer. I'm using a custom indicator called Pipfinite Trend Pro. When compiling my project, I get this error:
'StringConcatenate' - wrong parameters count
'iCustom' - wrong parameters countWhen opened in Meta Editor, the line of code that has a problem is:
StringConcatenate(key, Symbol, Period, "Market/Breakout " , (string)"==========================", (int)CurrentTimeframe(), (double)2.0, (int)1, (double)4.0, (int)25000, (string)"==========================", (bool)true, (bool)true, (bool)true, (bool)true, (string)"==========================", (bool)true, (bool)true, (bool)true, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (bool)false, (int)8, (bool)false, (string)"==========================", (color)DodgerBlue, (int)3, (color)Red, (int)3, (color)MediumBlue, (int)1, (color)Crimson, (int)1, (color)Aqua, (int)2, (color)Yellow, (int)2, (color)Blue, (int)2, (color)Crimson, (int)2, (color)Yellow, (int)1, (color)Yellow, (int)1, (color)Yellow, (int)2, (color)Magenta, (int)1, (color)Magenta, (int)1, (color)Yellow, (int)3, (color)Magenta, (int)2, (color)DarkBlue, (color)DarkBlue, (color)Maroon, (color)Maroon, (color)DarkSlateGray, (color)DarkSlateGray, (color)Yellow, (color)Magenta, (string)"==========================", (bool)false, (bool)false, (int)8, (int)8, (int)8, (double)2.0, (double)20.0, (bool)false, (color)Black, (bool)true, (color)White, (bool)true, (color)Magenta, (color)White, (color)Lime, (color)Red, (color)Yellow, (color)88,0,88, (string)"==========================", (bool)false, (bool)false, (bool)false, (bool)false, (string)"alert.wav", (bool)false);
Is something missing to correct this error? Thank you!
-
RE: Measure pips between two pointsposted in Questions & Answers
@josecortesllobat
Lmao.... I didn't even see that there was a Check Distance function on here.... I must have looked right over it as I scanned through everything. Thanks for pointing it out! -
Measure pips between two pointsposted in Questions & Answers
Let's try this. How can I measure a distance between 2 points? Let's say on some candle close, I would like to get the amount of pips from that candle close to the lowest point over the last 8 candles? Then, I would like to take that calculation in pips and compare it to a number of pips like 50. For example, is that number calculated from the above example less than or equal to 50 pips? Please..... Need some help on this. Thank you.
If this has to do with variables, please show me an example on how to use those. I have no idea at this point.
-
RE: New to FXDREEMA - MA . STOC Helpposted in Questions & Answers
There are many time blocks. Look at all of them. They are very self explainatory. Each one is a different amoun
t of time. -
RE: New to FXDREEMA - MA . STOC Helpposted in Questions & Answers
Use a Time Filter Block before the Buy Now or Sell Now block to avoid multiple trades opening.
-
Avoid opening trade due to size of riskposted in Questions & Answers
So, I am trying to figure out a way to avoid having my EA take certain sized trades. For example, right now after certain conditions are met, it will open a trade. As it does this, it looks at a range of candles to determine where the stoploss will go, (For a Buy Trade, It looks at the last 8 candles and places the stoploss 6 pips lower than the lowest price reached in that range, basically looking for the most recent swing low and placing the stop 6 pips below that. This is all done in the Buy Now block by the way). What I am trying to do is avoid taking trades let's say that are 50 pips or more from the point of entry to the stoploss. Since the stoploss is all calculated in the Buy Now block, how can I get this thing to measure the distance from the entry point to the stoploss point calculated and avoid opening a trade if the stoploss calculated is 50 pips or more?