@somporn69

Constant or variable is the same procedure.

@l-andorrà
The links between the blocks previously looked like this:

@tec-nacks
I think you can make what you want to do easier, I made an example for you that works. The Control Block is for control only. If it counts up with every tick, you know that the next block is switched, if not it is blocked.
But you have to do the rest on your own, this is the only way to get further in your understanding of the program.

https://fxdreema.com/shared/WS5iUoaGc

@mlumbreras
This can actually only be due to the expiration mode. You have to check that. I once inserted a control block for you, you can place it anywhere and you can then see whether the block is currently being run through and how often.

https://fxdreema.com/shared/kgmRSuKB

@mlumbreras
Interesting theory. I changed your AE something. You only need the "Pass" block if a block would otherwise stand alone or for special other applications. The "OpB" block is also not necessary, since something is only executed after an event, and "for each trade" is also not required , because the search is for the trade that JUST was executed. Maybe that will help you first, I didn't fully understand your description of how the EA works, but I think you need an additional variable, maybe.

https://fxdreema.com/shared/eye7h2kGb

@Pheaktra-Capo
Yes, the issue is a bit more complicated than you think. Of course, where your BEP is not only depends on the price and the volume, but also on the relative value of the positions among each other. You bought your selling positions all over the buying positions!!!
Here's another tip that you probably already know. If your positions are very close together and the sell volume only slightly exceeds the buy volume, the result is even a negative value. You can use the following example to help. If you hold the same volume of long and short positions, you have a hedg (profit or loss is frozen and stays the same no matter how the price moves). If the buy volume is only slightly higher than the sell volume, you need a huge price increase to reach your BEP because the sell position is also getting bigger. If you use the formula, you also have to insert a block with the function for the hedg. This can look something like the picture.

You only need to press the 3 dots and then you can change your post, you can then delete everything and write e.g. "deleted" there. But only you as the author of the message can do that.

Hi Paul, yes this is working fine now. I always use the function. If you always want the top blocks to start with a "ten's"(10; 20; ....), you have to replace them, but the logical order is preserved.

@jstap yes, it could be, it was just a way of thinking

@roar
Thank you very much, a very useful tip, I also had this problem occasionally.

@RGoo ......

deleted...

@roar
Thank you very much, a very useful tip, I also had this problem occasionally.

@Mitchp

Here it is better to use candle "1" because candle "0" is also the market price, although not the middle one but it could be due to such a constellation.

@Cybust
Interesting thought, I quickly put something together for you, take the DAX 40 from 2023 with this setting, that should work, what do you do with it, what is the strategy

https://fxdreema.com/shared/OWJt2e11e

@jstap yes, it could be, it was just a way of thinking

@Khun-Som-Ath
Ok, to do this you first need the BE, then you can add your TP to this. Here is a link with which you can calculate the BE SEPARATELY for buy and sell positions. You can also calculate the BE for both together, but that is more complicated.

https://fxdreema.com/shared/RJCz148ud

@jstap
thanks, it worked

@jstap , @sktsec
Thank you for the answers, I forgot to write that I don't need the current time frame to be displayed, but rather a time frame that I have stored in the constants. So I would always like to know which time frame my indicator refers to in the current time frame. Here are some pictures, all the code wouldn't be helpful.

Hello, does anyone know how I can display a timeframe value entered in the constants in the display? FxDreema doesn't know the TimeFrameToString(TF) function and returns an error message.