Topics created by Mantadiver

@mantadiver You're welcome.

Old thread, but it still is an annoying feature especially with equity protection and modifying daily drawdown settings etc when you don't want to re-apply the ea but change something. I had to make lengthy condition checks and variable inputs to check if any specific settings have changed.. doh

image.png

I have just noticed that when you hover over a variable name in the variables window it highlights the visible blocks that contain that variable.

Far out.

Not sure whether that's new or been there forever but very welcome all the same.

Great, many thanks.

Hi @kave
For me the solution was to stop using the auto-import & use Custom MQL Code blocks to import custom indicator data by using iCustom.

The issue may have been caused by the fxDreema import or maybe something in my custom indicators, either way, writing the raw code to import inficator values works 100%.

Hope this helps.

This is clearly a question for roar or miro. That question is advanced fxDreema knowledge! 😄

OK, many thanks for the clarification.

Of course ! I keep forgetting something this powerful is in the browser. Many thanks.

OK thanks, it's not material, just aesthetic !

Works great, many thanks.

There is no block to change this value, because the value is an input parameter and in my opinion it is not supposed to be modified in the EA. Actually if you try this trick in MQL5 you will get an error message.

In the EA, in all trading blocks you can find this Group parameter. If you want to somehow have 2 or more strategies in the same EA, you can try do it with this parameter.

This mouse-wheel feature simply works over all input fields in general. I personally use it a lot, because I'm lazy to type on the keyboard. And I'm used to move the mouse away from such fields when I scroll 🙂

Most people don't have so many variables, but I see that there is a bit of horror going on when their number is so big. I remind myself to do something about this, but I also remind myself of other things 🙂

Excellent, many thanks.

The candles I am using are achievement based and therefore each one has a different amount of time.

I have resorted to:-

a) Running a continuous bar count on each bar open = (Current Bar Number)
b) Recording the current bar number when a new trade is placed = (Trade Start Bar Number)
c) Calculating the number of bars between now & when the trade started = (Current Bar Number) - (Trade Start Bar Number)

A little crude and simple but appears to be working.

Many thanks for the input.