Posts made by l'andorrà

@shubhankar-kumar AFAIK that is not possible. What you can do is opening a trade with a market execution at a specifoc price level.

@ecowith You can do this:

@talalkhan In order to do a complex project like that you will need a separate structure to identify the increasing value of lot size. This is the simplest example I created some time ago. I hope it helps:

https://fxdreema.com/shared/6o0uTdg3e

@pyrziel But have you ever used UNIX time? Have you ever seen how it shows? It is a number like 1636554284, for example. This was a real example (UNIX time when I type this reply right now). You will need to translate that number into component if you want to understand it-

@andrewfrank The second condition searching dor 0 crossing is easy. You can do this:

Finding the 'highest/lowest' is more difficult. How is a high or low defined? Is it a local high, daily high or something else? Depending on that definition dfferent results can be obtained.

@haikel Well, I'm also trying to understand the admin's reply. I'm not sure what the solution is. I hope he will let us know there.

@talalkhan Here you have an example for the highest:

https://fxdreema.com/shared/z3DhmXMtd

Then you can try for the lowest woth a different variable.

@fxdreema What do you exactly mean by 'you forgot to set at least one of them'? All of them are set to 0 by default as you can see in the Constants. Should I remove any of those .set files? If so which ones?

@vonmunchy Interesting. Thank you for sharing.

@fxdreema So are you suggesting that we should not use any value 0 for any constant that is used on any indicator? I think I understand the problem, but not get the solution, sorry.

@haikel I'm afraid this is another unexpected consequence of the last MT5 update. You can find some guess here:

https://fxdreema.com/forum/topic/13646/anyone-knows-how-to-deal-with-error-4002/14

@pyrziel Time optimization is very tricky. You can do it by using UNIX time, but you will need to transform those values into components if you want to visualize it easily. That is not a trivial thing to do. Do you really need it?

@suleyman-0 The problem with those strategies id identifying when the first buy is supposed to be open after all those sells. How would you do it?

@acealert Can you please share the link to the project? That will be easier to check the issue?

@flockogola Do not use negative values for candles. What you call candle -2 is called candle 2 in fxDreema.

@nehemiah7 What do you exactly mean by 'bullish tick'? Do you mean a higher price value now than the previous tick, maybe?

@talalkhan Is the EA removed form the chart regularly? If so, that would make it more difficult.

@paihdt You can remove both 'once per bar' blocks 40 and 41. They are unnecessary. Then you need a condition block below blocks 33 and 37 comparing the current value of lot size with that maximum you want. Depending on the result that same lot size variable is modified accordingly.

@tigriyorfeo Necesitas crear una variable que haga las funciones de interruptor. Con una de tipo lógico será suficiente. Haces que se reinicie automáticamente al inicio de cada mes y que se apague al conseguir el objetivo.

@kestra Firstly, you can remove all those 'if trade' blocks on top of each tree. They are redundant. Then you need to create a specific structure for the martingale. You will not be able to make it work as you want with the money management option on both buy/sell now blocks. However, that will not be easy. Here you have an example to create a fully functional martingale:

https://fxdreema.com/shared/6o0uTdg3e