Hi Alepie,
thanks a lot!

Thanks a lot.

Why MT root? 😮 fxDreema must know the root, but it writes files in "/eperts". It adds "/experts" automatically, so there is no need to put it.

The system can always be better 🙂

Well, you can search if there is a trick to do that. I remember that once I searched for this and didn't found a solution. If you ever find indicator, ea or script that can write such a thing, show it to me 🙂

Thanks for the replys. It will be no indicator but the EA should also show you what the EA will see within the price action and why it took a trade. So i draw some rectangles to show what also had been in the past.
I already removed the return statement 😄 . That was pure nonsense from my side.

At the moment i try to use some MQL block to shrink the number of blocks. But what i like to see is to shrink the opened MQL-code box more than it is possible at the moment.
The overview of the EA is nat that good and a block with a short label can't express what i do in it...

Hope i will get around the error i see at the moment and why the CurrentBar value can go under 0 when there is block to catch it and it why it will be executed till error... ❓

Okay. I tried this within a print message block but it gave me an error. Will try it again and report 🙂

This can not be done in fxdreema at the moment

Check in "Condition" -> Price levels

Yes, "Volume size" is the lots you are going to trade. Some brokers allows 0.01 lots, others 0.1, but if you set a value that is less than the broker's minimum - the minimum is taken.

Sounds good to me. Keep on ⚡

The normal way is to use buffers of course, not the objects. There is a block with name like "Levels tester..." that can show visually how any buffer behave.

Actualy I was asked for the same thing before. I thought that "starting from" is enough to describe what is that price means, but probably for some people has no logic. It's maybe because I am not a native-english person. But the truth is, it's better if everything is written in a way that a 5-years child can understand it, so I rewrote that text with another that sounds better... I hope.

Thanks for the info i did this just an hour bevore 🙂
Now it looks better...

Keep up the good work. Sometimes its really fun to work with FXdreema and i know that i can work faster than with programming the EA in 'text'-mode 😄

To know if some indicator can be used, and how, I created "Levels tester" block. Connect this block with "Just pass" and load the custom indicator inside. Choose one of the buffers available. Run that EA (in visual mode) and in the chart you will see levels of the buffer.

Basically what I need is:

open a buy and a sell with same size lot and TP (no SL) the first one that hits the target opens a Grid with negative grid size. (supose the sell hits the TP it opens a grid buying as the market goes down those buying are triggered increasing the size lot and the TP) open the same order of the first hit again (continue to open sell orders with same lot size and TP) When the first buy order (the last opened) hit the TP the EA close all orders and delete all pending. Start from number 1 again

So the EA keep opening orders with the trend with same TP and size lot
And opens opposite orders increasing the size lot and the TP (reversal grid)

Something like this? http://fxdreema.com/shared/Uzvugs75d

When backtesting, white checksigns are the moments where it tries to close the trade, yellow x-signs are the moments where it says that no close will happen on the next check.

Those 3 blocks on the right are optional, they does not matter in the strategy and can be removed. Block "a" is connected between "5" and "10" because otherwise "10" changes the environment for "a".

Every "n" minutes - this is a block who can pass once at the last minute in the period. When started for the first time, it does not pass.

Thank you loads for your help. 😄 I will follow the guideline of your suggestions.

At the moment I work for a new thing that will probably help many people with debugging the project, and Library Studio is with lower priority. I can't give you a promise when I will take care of it, also because this thing is still not really clear in my mind 🙂

http://fxdreema.com/shared/SVoHH5JFb

Guys, I really want to know how do you work with indicators that changes behaviour multiple times per bar. Most of custom indicators are like this, are they made to be used with at least 1 bar shift?