@cesardefez You're welcome.

@vanderleyfm Ok. Then just substitute the block I suggested you in my screenshot by a 'For each position' one and store the TP price as I show there.

@stoopfex I simply don't understand the logic of thos project. What is block 635 for? And why blocks 1 and 326 are from different timeframes? I think this is the origin of the error.

This topic is no longer important. I have a new topic here
https://fxdreema.com/forum/topic/11507/buy-close-and-sell-close-strategy-someone-can-do-it

@remzeal Please create a new thread with your request. I will not answer any more posts here.

Hi all, (I realise that this is an old thread but i'm just replying to add info for anyone like me who googles this in future)
Thanks for the condition info miro, the blocks didnt seem to work for me but I slightly altered what you'd done and now it works for me
.png image url)

@cesardefez In that case I cannot help, sorry. I have to admit fibos and buttons are not my field of expertise :(. I hope someone can help.

when pressing the button, a fibo is drawn and it remains selected. when drawing the fibo I turn off block 140
Usually it always puts the same name, but just in case I verify it in fibo properties.
what I hope is that when I deselect fibo, I activate block 140 to put operations.
I don't know why it doesn't work for me.
can someone check it out,?
https://fxdreema.com/shared/EpjSRUS0d
Thank you

@skauch Considering how small your project is, I recommend you move all blocks on the 'on timer' tab to be moved to 'on tick'. On the other hand, I would recommend you to use 'server time' only in all EAs. Then do the math to be sure that you are choosing the right time according to your broker's server.

@cesardefez AFAIK those errors are identified in the logs only. I'm not sure logs can be read, but maybe I'm wrong. Can anyone confirm this is so?

solucionado..
0_1608731978752_137304f2-5365-4e20-9a44-ab2fa9ce8747-image.png

@meken I see you are using an ex4 extension. Sadly fxDreema is not good at identifying buffers in ex4 format. You should import the mq4 version instead.

@legitimate Obviously we are not understanding each other. 🙂 Let me asi it this way: is that 10% exactly the same AFTER or BEFORE the original trade hits the TP?

@skauch Acording to your settings, the trailing stop will not activate until proce is AT LEAST 40 pips away from open price (see TrailingStart constant). This is why it doesn't move. Price is BELOW that pips distance in your screenshot.

@1122kmc Man, you are looking for the Holy Grial! 🙂 Good luck if someone does share it.

I hope so It will Be so Great To have one like that

@skauch Exactly, but you should swap ID numbers. Block 11 should be renumbered as 6 and vuice versa. You always want the break even condition to be checked first.

@princeclaw You will need a loop dearching for those past candle ID values in the past. Candle IDs are dynamic. This means they cannot be stored into a variable. This thread will be helpful for what you need:

https://fxdreema.com/forum/topic/10774/is-there-any-way-to-store-rsi-value-when-a-candle-closes-at-its-high-or-low-and/7

@l-andorrà said in Extend stops on every new order...:

@legitimate This is the third thread you create with the same topic. Please focus just in one of them and do not duuplicate it anymore.

sorry for that, just help me with the last.