"Constants" and "Variables" in fxDreema are basically the same thing in MQL4 and MQL5 - global variables. The difference is that Constants are automatically set as input parameters (to be seen in Inputs list), in other words they have "extern" (MQL4) or "input"(MQL5) in front of them. What is specific in MQL5 is that input global variables cannot be modified inside the code, while in MQL4 they can... but I will recommend to use Constants as constants in MQL4, to not modify them in the project. Also, you can't define Constant and Variable with the same name... at least this will not work in MQL4/MQL5, you will see an error message.

But you can define a Constant (if it should be in Inputs, otherwise a Variable will also work) like "Hello" and a variable like "vHello" and set "vHello" as "Hello" in order to "reset" it.
If I'm gonna do the functionality to reset variables, it will be something like this, but... now I'm not so sure that this is a great idea, because now you can set a Variable to be Input (to be Constant) and if there is a functionality to reset that Variable... well, in MQL5 it will not be possible, and I also know that MetaQuotes are in process of changing MQL4 to be the same as MQL5.

Thanks Seems to be working now.

Cheers

Got it now! Thanks again. 🙂

Yes, currently each block creates it's own function and if you use 2 or more same blocks, they can write the same things 2 or more times, and this creates a big file. Well... big for download and process before downloading, otherwise for MT it is ok.

What a shame! Get 058 again. Then to create a new custom block, write something in "new block..." field and hit "New" on the right.

Yes I saw one of your posts in which you warn about the fact the Strategy tester is not always reliabale, and if I rememeber correctly the main isue was with 1 minute time frames and that 5 minutes and up should be ok...?

Anyway, I'm past the days of buying "black box" EAs. Today I have the knowledge to design my own EAs and the methods for that are either using FXdreema or hiring a codder. I prefer the first method for many obvious reasons but again time is an important factor for me at the moment.
I will start having a look on your documentation.
Thanks again

No, the block should work, I think it's fine. You can always backtest it without crossover above it (with "Just pass" for example), and it should close trades immediately when they go to certain profit. Also you can check if crossover works by putting "Draw arrow" or something else to be drawn after it. Then you have the combination of both, which should work as well. At least it works on my backtester... and I don't know what can be wrong with the project itself, so I'm thinking about input parameters or point format or something else that is hidden. But if you can't understand what is going on, I can connect to you with TeamViewer.

Adjust field. You can write there something like "+0.1"... what you put there will be added to the value of that operand, and you can actually see the result if you see the source code of that block (right-click and hit "Source code").
Status field - this will change what you see when you run the EA on the top-center. This place where normally it says "Starting..." and "Working".
Comparison field cannot be used to write something there, this is a normal html select (drop-down) field.

It's always better if someone understands MQL4 or MQL5 here on this website. Or basics of programming, no matter what language - I mean functions, definitions, variables, constants, statements, arrays... If you have questions about this, ask them.

In case of Buy trade, SL is initially below OP and cannot be placed above it, but if there is a big enough profit SL can be placed above OP, because SL depends on the current market price, OP does not matter.

When we have just placed Buy trade with SL of 100 pips, we know that SL level is 100 pips below it's OP, which is the current market price as well. And even when the price goes above/below a little bit, we still think that SL is 100 pips, because we accept that it SL is calculated as the difference between OP and SL level.

But what if we are in profit with 100 pips and we put SL 10 pips below? Then, how big is our SL if we measure it in pips? Can we now tell that SL is the difference between OP and SL level?

So, now I realize that this option (% of SL) is not very correct, because it is fine only when SL is below OP. Well, if we say that SL (in pips) is the difference between the last market price when we opened/modified our trade and SL level, then everything will be a little bit better. And in MQL4 we know Open Price of any trade, but unfortunately we don't know the last Modify Price, there is no such attribute in MQL4...

Then I decided that I can save that attribute in memory, but everything will be gone when the EA is turned off by accident, and the strategy will be bronek. So I decided that I can also backup that data in external file, but actually almost the same problem goes here - if you modify a trade manually or with another EA that does not operate with this external file, there will be wrong data again.

In Martingale blocks check this "Maximum volume size" parameter. If there are history trades, they are used in the strategy.

Cool thanks.

Any idea when a trend line block would be ready?

looks like the monthly data is there and goes back 5+ years. Seems to be working now, thanks.

Try with the other comment block with content "". But I think this block is not very good and I will probably do something with it.
Or try with Custom MQL4 code with this content:

great, I'll give that a shot 🙂

Nice. And this happens when the same variable name is defined in Variables and Formula block. It will be fixed.

That's great! Glad to know that the fault is on your to do list. I'll work around it for now. And thank you also for the extra bonus! Most generous, and much appreciated by me! 🙂

Ah. Yes. You did mention this before, and I'm sorry I forgot! However, I still think it would be useful for other users to be reminded that if a numerical system is used with controlling blocks that the numbers will need changed. And probably the best way is to have a small pop-up with a reminder and a "continue" or "cancel" button.

Thanks again. 🙂

Get this now: http://fxdreema.com/desktop

I hope it will work. Thanks for reporting that!

Out of http://fxdreema.com/examples => http://fxdreema.com/demo/mt4-4765
These are events. When a tick comes - blocks under "on Tick" are executed. "on Init" is when the EA starts. "on Trade" is when trading operation occurs - new trade, close trade, modify...

Yes, there is such a problem with Windows 8, I still don't know why. Unfortunately in the moment I have really bad internet and it's hard for me to update it.

But web version and local version are the same, so you can use web version. I checked your current project, and to use "Break even" under "on Trade" is not really right, it should be used under "on Tick". And I tested this project and I have a trade. Do you have some errors?