Posts made by l'andorrà

@pedrio Puedes hacerlo así:

https://fxdreema.com/shared/Eojig2Mse

En este ejemplo, cuando el repcio alcance 50 pips en beneficio, el SL se moverá a 3 pips por encima del precio de aperura si es una compra y por debajo si es una venta.

@akulus Can you please share the link to the project instead? That would be easier to check.

@ladydolares You can try this:

@heapssickhey19 You are requiring that the second alert happen at the same time as the fisrt one (they are connected). This is why the second one never arrives. On the first one, you selected candle close crossing and that is not the most efficient way to require it. Instead you should specify (in two blocks) that open price should be on one side of the MA and clos in the opposote one. That will be understood for sure.

@mark-7 Sadly, all crypto payments are confirmed manually so it may take up to 1 week. Just let the admin know via email (again) the day you paid. Then he will extend your subscription as many days as necessary. Sadly, he may take one week to reply. welcome to the terrible support service of fxDreema!

@frank-2 Not sure what you exactly mean. Can you please be more specific?

@crazycnw said in My EA does nothing:

shared/oTgHrvqcb

That 'once per tick' block is unnecessary on the 'on tick' tab. You can remove it. On the other hand you can use variables instead to show that above/below text. IIRC that feature was designed years ago and not updated so probably it doesn't work as initially intended.

@william-1 I see one condition block only. You should add one for each candle comparison. Additionally you need to add one 'bearish/bullish candle' block per each one you need above each previous condition. Otherwise the EA cannot know wich candles are supposed to be checked.

@meken You will need to use groups definitions per trade. Do you have an initial project to begin with?

@sauce I wish I could, but I have no idea how code can be fixed. I'm not a programmer, sadly.

@alphaomega No problem, man.

@wadz91 That specific sequence will require a specific loop to do that. If it is fixed you can do it with variables. However, if you need different sequnces that increases complexity exponentially.

@amincgi Interesting. I cannot edit with fxDreema. Did you block it?

@jithin Not sure if this can work, but you can move the buy/sell blocks to the 'on timer' tab to see if you can delay them there. You will need a variable to control that, of course.

@ace-fx I'm also interested in that question. I'm looking for exactly the same feature. Any help wil be appreciated.

@kevdiaz Es complicado. Los bloques de fxDreema sólo contabilizan el flotante de las operaciones abiertas, no de las cerradas. ¿Tu cuál necesitas?

@andrewfrank I'm afraid fxDreema cannot be used to create indocators but EAs only.

@kriordan Then I canoot find a reason other that any incompatibility between the indicator and fxDreema. I recommend you should contact the admin and let him know.

@lanrayy That's a huge EA to implement. Searching for info that happened in the past requires complex loops that are executed over and over. Certainly not a trivial project. In order to simplufy it, I would recommend to hire a programmer to create an indicator searching for that past info and then we can embed it into an fxDreema EA. Otherwise this would become a colosal task to do.

@gu95ckt8 You need to use one separate block for each ID user.