Topics created by jzfusion

@jzfusion You're welcome.

@jzfusion Loops are not always easy. I'm afraid thaey are not my field of expertise, sorry.

@jzfusion Probably. What data quality is your backtest? Never trust anything below 99%.

@cmk No. This block considers that if the trade is in profit you need to specify negative values, no matter if it is a buy or a sell.

@jzfusion try using these lines of code:

vdSwapSell=NormalizeDouble(SymbolInfoDouble(Symbol(), SYMBOL_SWAP_SHORT),3);
vdSwapBuy=NormalizeDouble(SymbolInfoDouble(Symbol(), SYMBOL_SWAP_LONG),3);

https://www.mql5.com/en/docs/marketinformation/symbolinfodouble
https://www.mql5.com/en/docs/constants/environment_state/marketinfoconstants#enum_symbol_info_double

@jzfusion You are using the 'adjust' box incorrectly. No Constants can be added there. What you need to do is typing manually +High or -High in one block and +Low or -Low on the other one depending on what you want.

@jzfusion Just look at price behaviour when one is above the other. Then you will be able to adjust when you thing prie is trendy or not. Ther is no 'magical' solution, I'm afraid. 🙂

@jzfusion I have no idea. I suggest you to ask that directly to the admin. He'll not reply soon, but he will for sure.

How about closing trades basses on rsi overbought and oversold ?

Can you please share you project? I guess there is something missing behind it all.

Will it be the same account but on different platforms? In that case you will still need a programmer, I'm afraid.

@roar
excellent... thanks

@trader-philipps said in How do I have drop down parameterised for optimisation:

@jzfusion Define a constant for the desired field

For MA method use datatype ENUM_MA_METHOD
See valid values (for default value) here: https://www.mql5.com/en/docs/constants/indicatorconstants/enum_ma_method

For MA price use datatype ENUM_APPLIED_PRICE
See valid values (for default value) here: https://docs.mql4.com/constants/indicatorconstants/prices
0_1582771088133_9b6a7b68-d3d8-4338-ad4e-414b8872ffcc-image.png

Once you define the constants, you can use them each time you use the MA indicacator by rightclick on the correspondant field.

0_1582771210843_908138b5-3579-4938-9548-170c585e2eb6-image.png

Is this really your use case? You might try to use integer variables starting from 0 for the choices. But as the number of input fields vary from the choice I think, best approach would be as @l-andorrà says to use a custom code block for that.

@ambrogio
That's very helpful

Your current distribution of blocks means that when ANY condition on blocks 10, 5 and 12 are true, a buy will be open. So yes, positioning them on parallel has that effect. Did you try to choose cond 1, cond 2 and cond 3 as false when setting your input parameters? That is the only way not a single trade should be open.

@jzfusion In Tutoriak EA I use those settings ..

0_1582153576937_3dc814a1-7971-4741-9ab0-7115f628495c-image.png

This means, if a stop for instacnce is 10 pips away from openeing price, the real stop (enmergency) would be 20 pips.

So in total you have 2 options:

A multuplied value of virtual stop A fixed amount of pips

If you use virtual stoops, you may have to consider some functions such as if last trade was closed by SL for instance. I think that won't work with virtual stops as the trade was not closed by SL but by EA. But I haven't tried it yet.

You will need to create a variable and then follow the idea here:

https://fxdreema.com/forum/topic/8188/how-can-i-round-a-number

In general, a 'For each position' block should not be used in the same structure that launches trades. It is a loop block for already open trades!

Ok. Thanks.

@jzfusion Try this way
0_1581362285797_Cattura.png