Posts made by fxDreema

In USDJPY, what price distance is 3 pips? If you place SL or TP something like 10 pips, where it will be placed?

I checked this EA and it seems to work. If you want, put "Once per bar -> Draw arrow" after block #4 just to see places where crossovers occur. When this happens below my Sell trade, it's closed.

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.

Yes, but not exactly in the way you describe - if X happens, and then Y happens, do Z... It's better to think from Now to the Past while creating conditions for EA, because MetaTrader knows old values of candles and indicators and in order to decide to do Z or not, you only have to ask Now if X and Y happened in the Past.
But of course there are situations when this is not the best way to do it, then Now you have to save value in a variable (or more variables), let's say that this variable describes some event, then in the Future check that variable in order to decide to do Z or not.
In other words, when Now you have all the data needed (in the Past) - use it. There is data available about candles (O, H, L, C) for all timeframes and symbols (well, MT4 can backtest only one symbol), indicators data is also available. And when you don't have something that will be needed in the Future, save it to the memory Now, but note that when you restart the EA this memory will be cleared.

In your condition you have Bid + 1. If for example Bid is 1.3243, then 1.3243+1=2.3243. Better use +0.0001 or +1pips.

I'm not sure if I understand all questions, but in general, in fxDreema - Constants, Variables and Results (Formula block) are all global variables in MQL4/MQL5. Constants are always input (extern, input), while Variables are not by default, but can be (there is a checkbox). Formula results are not input.

In MQL5 you can't modify global input variables (with "input" keyword used). In MQL4 you can, but I can recommend to use Variables as variables, and Constants as variables that will not be changed in the project (that's why I named them like this), no matter if this is possible in MQL4.

Constants, Variables and Results can be used in all blocks if you write their names somewhere. Or in case of Constants and Variables - by right-click and choose some - in this case the block gets the Constant/Variable by hidden id number, so you can then edit any Constant/Variable name without affecting the project.

You can do much more if you know how to program... a little, because you can always create a custom block and write things there. In fxDreema, to modify one variable you use a whole block, while in a custom code you can put as much code as you want (1 line, 10 lines, 100 lines...).

Because you want to work with indicators, you must know about their buffers, how to deal with indicators in EAs. This is important because every custom indicator is different, but they all follow same basic rules, and when you know those rules you know every custom indicator. After you understand what indicator buffer is, you can use one block with name "Levels tester..." to spy some buffer (to see what value is in the buffer in realtime), and when you know that you can manipulate it's values the way it's needed. But there is also a category "Indicators" with some blocks that should help this process. For example, to detect when arrow appears, use "Indicator appear" block (you have to know which buffer corresponds to the arrow). Also notice that some custom indicators have nothing on their buffers or have a mess there. The other things... later.

Try with "SAVE" button, I will check what is going on... And sorry for that problem!

If you select variables with right (and choose it), there is no need to do something in blocks, you can always rename any variable, because they are associated with some ID that is hidden from user. But if you wrote the name manually... well, in theory everything is possible, but now there is no an option to search & replace in fxDreema blocks, but it's a great idea otherwise and I will include it to my to do list

No, but there is a way to modify things on fxDreema and not work with MetaEditor

In MQL5 global variables used as input variables cannot be modified. This is allowed in MQL4, but not in MQL5.

Of course, it does not read MQL4 code, it reads the special code at the end that contains project data.

Block IDs matter when you have blocks connected in parallel - the ones with lower ID are executed first, so in this project the first block to be executed after 310 is 166, then 313, 314 and 314. I can recommend to connect calculation blocks one after another, not in parallel.

This simple example seems to work: http://fxdreema.com/shared/Pg8gzq4P

I think the problem is something in Formula blocks or the way they are connected. I can recommend to not use so many variables (Results), you can modify the same formula result in multiple Formula blocks. Or define variables (click on Variables) and then use "Modify Variables" block. The idea is to make it as simple as possible with less variables and blocks.

Yes, maybe "% of Stop Loss size" option in TS is not working as expected in all situation. First, because to "start trailing stop" means to do trailing stop when the condition is met, otherwise wait. And second, this Stop Loss size is calculated as the difference between Open Price and Stop Loss... which is fine when SL is below OP for Buy and above OP for Sell... but in your case SL is already on the opposite side and then that difference is not correct. Now the question is what is the SL size (if you measure it in pips/points) when it is modified while the trade is on profit and OP is on the opposite size. Maybe it is correct to say that SL is the size in the moment of modification (Ask-SL for Buy or SL-Bid for Sell), because after that the price continues to move and Ask-SL and SL-Bid changes all the time.
I'm not sure if you will understand something. Now I'm not sure what is the best way to resolve this, but I will think for some way.
For now I can suggest to use other option for trailing start. Maybe "Fixed pips" option, where you can write exact amount from Open Price which can be calculated somehow.

You don't need all timeframes, but the biggest one - Monthly in live or Daily in backtester. I don't know about tickstory, I tested it once... long time ago...

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:

Comment("");

Upper_Part and Lower_Part are defined as global variables in MQL4 and they can be accessed from everywhere. You can use Value (numeric) and write variable name there.

Currently when you have Formula blocks, even if they are not connected, their "Result" variables goes into the final file, but I think this can be considered as bug and I can "fix" it some day... who knows.

Otherwise you can use "Variables" and "Modify Variables" block (or even Custom MQL4 code)... or custom block where it's easy to write some formula using known things