Posts made by trader.philipps

@maverick83 Remember that ADX is lagging a lot and hence you should have other confirmations as well.

@charlie66 It should set BE for both. At least it did when I tested it ?!?

@polishinglife There's something wrong with the indicator

Did you get it from the mql5 market?

@maverick83 Well, I have it build here but can't upload the mq5 file unfortunately due to permissions. Don't know what the issue is. So I'll make screenshots.

First I would suggest to specify candle ID 1 on where ever you reference an indicator as on candle ID 0 values still might change until the candle is closed.

Here is the close logic.

@trader-philipps Hey folks, the AllAverages indicator I posted above was anly showing ATR bands on the current TF. Here is a version that also shows the ATR bands on a higher TF (with higher TF ATR).

0_1578712531547_AllAverages_v4.9_600.mq4

@maverick83 That depends on the indicators. If both are in the chart and have a price value, you might use a condition block. Otherwise you might chain 2 conditions such as RSI x>30 and Price > EMA 20

It really depends. So if you have a project to start with, you may post a link. Or specify your conditions more precise!

@polishinglife I can click every optimization checkbox in the provided project link. Of course that may be due to the fact that I don't have any of those indicators as well.

Maybe you may share these indocators. Fxdreema is a bit unstable with non-roman characters in the indicator's code (even if those are only comments).

@hypnoise Okay, that was a tricky one. As stated before the issue is that both indicators use the same entities for enPrices and enMATypes. However, other than I thought before, it is not the enum datatype name itself, but each entity. The compiler complains for exampke that the entity pr_close is already defined. Changing the enumeration name did not help.

So the easiest solution I found was to import 1 of those indicators again into fxdreema and on the import screen delete the sections for enum datatypes enPrices and enMATypes.

Before:

After:

That worked for me in the end as fxdreema appears to import those sections into the EA and for the 2 indicators they are imported twice. Hence the compiler will throw an error. I don't know if that is a fxdreema bug or one would call it "works as designed".

Let me know if that helped you.

@charlie66 Here you go .. 0_1578696837127_10 pips.mq4

I implemented 2 ways. For BE I use the pips away block like you did. For SL to TP1 on TP2 I implemented on the onTrade tab if the 2nd trade was closed by TP.

I also introduced some constants in order to show how that would look like.

@hypnoise I will take a look later today. If you have any updates on your project, please re-share it.

@zarbitz First start to read this thread https://fxdreema.com/forum/topic/8486/multiple-tp-tp1-tp2-tp3
I will upload my project as well tonight there.

@charlie66 Ups, sorry I built your project yesterday but forgot to upload. I will send it anyway when I'm in front of my PC.

@zackry Should work. I use it the same way in one of my current projects in order to use an indicator on next higher timeframes.

@charlie66 That's a good one. I'm thinking of it since some times as well. There is a simple solution and there may be some not so easy ones.
The general issue is what happens if you close your terminal or change the settings of EA or casely close your chart and re-open it from the deleted charts. If you work with regular variables, those would be lost in all the stated cases. You might think of terminal variables maybe, but I haven't tried it, yet. The most reliable way would be if you could at any time recalculate your take profit targets, but that depends on how you calculate them.

First the simple one: Split your order into 3 orders and each with 1/3 of the lot size. Set your TPs accordingly to your calculations. You may use groups for each different TP target. And finally you create a block path on the onTrade tab, where you do the following. If closed group 1 trade set group 2 and group 3 to BE (or wherever you want it) and so on

If you want to keep 1 order, than as stated above you need to store (or be able to re-calculate) the take profit targets ar any time and store them in variables. You also need to care about the case that EA ghets reloaded while trades are open. Then you'd check if profit target variables have a sensful value and if not you'd recalculate them.

Basically I've done both ways already in some projects. If you have some experience you may chose the second approach. Otherwise I'd recomand to choose the multiple trades option.

@hypnoise Well, it looks like that both indicators use the enum datatype for moving average type. I'd say if you have the soureces of one of them rename the datatype and reimport the indicator.

You may share the mq4 files and I could try by myself.

@roar Yepp. I solved it that way

https://fxdreema.com/shared/3UxuF33Yd

@harvey SPAM

@seb-0 If you share your project and tell us what you try to achieve we might help you.

@seb-0 I Think that was @ambrogio 's code. However, if you're interested in determine the timeframes (current and next) you may check this thread https://fxdreema.com/forum/topic/7723/call-a-function-for-calculating-next-higher-timeframe-solved/3

@luisd72 Like @ambrogio showed is what I meant!