Posts made by fxDreema

Noooo, with using pink blocks it can be more optimized, if one loop is used for many purposes. The problem is that the number of blocks becomes bigger.
There are loops everywhere - in every blue block, in every brown block, and this is because in MT we can work with multiple trades at once and in order to control them we must select those that we want to work with.

SL and TP are levels in fact, price levels, like 1.3456. There are options to get SL and TP as pips, but sometimes this is not a good idea. If SL as pips is the difference between OpenPrice and StopLoss, then what is SL as pips if after trailing we have our StopLoss on the opposite side of OpenPrice?
But to just check if there is a SL or TP, it is enough to check if they are > 0.

Hm, something went wrong few steps above your last point. You tried to normalize IDs? Maybe there is some bug in this functionality...

Anyway, I moved your EA back in the history with few steps. Do something starting from there, it will overwrite the next steps.

This block resets counter by ID number - see in the properties of this block and also in the counter block that you use. So the reset block is not connected with the counter block directly, it can be placed anywhere around connected with other blocks, it only gives command to clear the counter with given ID. It's like you have a variable that you increment somewhere and you modify it to 0.

I don't remember exactly, but I think that each counter block should have unique ID, but I might be wrong and they probably work as groups - for example to reset more than one counters at once

Cross width is number of candles between both crossover points. To mention again, the candles in between are not used in this type of crossover, but maybe I will do it that way in future. Now it is simple as that:

• Line A crosses Line B below when: A[new bar] < B[new bar] and A[new bar + cross width] > B[new bar + cross width]
• Line A crosses Line B above when: A[new bar] > B[new bar] and A[new bar + cross width] < B[new bar + cross width]

This is normally for applied price for indicators:
http://docs.mql4.com/constants/prices

http://fxdreema.com/demo/using-trade-event-tick

You can always try what will happen if you change parameters on the fly. It works, but I don't remember if there was something that will not changed.

Magic number is a property of all trades and pending orders, just like SL or TP, it does not depend on any other property.

If you mix pink blocks with blue blocks... just read the description of "Foe each Trade" block to get more clear what is going on. Also read the description of "Close trades". In MetaTrader 4 there can be so many trades at once, if someone wants to do something with one of them, he must point to that trade and not any other trade.

SL and TP size of a single trade/order can be checked with "Condition" when "For each Trade" is placed somewhere above. Find the special pink category in "Condition".

Also play with "on Trade" event, it can be used for some interesting purposes.

Blue blocks always pass. Read the description of any block to check what it's outputs are programmed to do.

There is an event called "on Trade" that can detect when TP or SL is placed. Otherwise you can always check if some trade has SL:

For each Trade (set the last parameter to 1 to work with the last trade only) -> once per trade/order -> Condition (somewhere in the pink category there is Stop loss and Take profit)

In that Condition check if SL or TP is > 0 and then do what it has to be done. If I don't miss something...

If you have TeamViewer, send me your data on PM or email.

Let's say I don't understand what was that, but I just updated "Hours filter" block to accept string values. If someone finds problems with this - you are to be blamed

Damn, looks in a way that I don't like But is it correct? These "Set Timeframe" blocks are to used at the top, not at the bottom... well, it depends maybe. What is that matrix, can't it be simplified somehow?

For those blocks "Hours filter", "Minutes filter" and other time filters, I was even close to decide to remove them after I added "Time filter", as "Time filter" should cover them in a better way. But there is always better way

Well, some programming rules should be follower. For variables names use latin letters, numbers and _ symbol, start the variable with latin letter or _ symbol. As I said variable names are not important, but in the meaning that it is not mandatory for them to be exactly the same as those used in the project. But they are variables after all. There are valid:

VariableName
Variable_Name
_Variable_Name
Variable1
_Variable123

These are not valid:
1Variable
Variable Name

• Variable name
  // Variable name!

In case of string variable, better don't use symbols like ", //, /* or */ - these should be escaped... and I think I was not implemented this right now, or I have to check if this works. I will add some filter & fix rules later.

I tried to add more than 10 variables in my sample indicator, there is no probles at least here. But try to do things in the way I described above and it should work.
Basically, for all variable names everywhere use variables that only contains latin letters, some numbers (but not as first symbol) and underscores.

Are there problems with the server? Otherwise in the moment I'm working for an update that will make projects on the client side to work much more faster, because now when you have many blocks it feels like something heavy, and this is because of the javascript script that is used to handle blocks.

I don't know, I personally don't have antivirus things on my laptop, but I just checked it with some online tool and it says that the file is ok: https://www.virustotal.com/bg/file/eaee ... 387404306/
What is that "Win32:Evo-gen__" means?

Because it is one of the oldest blocks and I was not changed its inputs, but there is a "Minutes filter" block out there, and also "Time filter".

Variable names does matter, the same with buffer names.
What matters for input variables is their number and datatype. There are 3 basic datatypes - string (when variable is text), double and bool (when it is true or false). We can even generalize datatypes as 2 main groups - string and not string.

int = whole numbers, like 24
double = float numbers, like 24.5
bool = true or false, and these are keywords for 1 and 0
string - any text

So if you see value like 1 or 2 or 3 or 24 or 18328, this is int. But double will work as well!
If you see value like 1.3 or 2.4 or 126.283, this is double, and int will almost work... but not exactly.
If you see value like "Hello, world" or any other text - this is string and no other datatype can replace this one!
if you see value like true or false, this is bool. But double or int can work as well (with values 0 or 1)

Again, the name of the variable does not matter, because to get a value from custom indicator, the special function iCustom() is used, and there you only define values as they are.

"cross width"? This is very simple one that I have to update, now it just allows you to compare the current candle with candle+cross width. Normally for crossover you want to check candle X with candle X+1. In the block it's actually candle X with candle X+cross width. If cross width is 3, 4, 5... the candles in between are not checked at all, at least at the moment

The idea is to have 2 block chains under "on Tick" like this:

No buys => Check condition to open new Buy => Close all trades (or only sells, but there are no buys anyway) => Create new Buy
No sells => Check condition to open new Sell => Close all trades (or only buys, but there are no sells anyway) => Create new Sell

Depending on the condition "Once per bar" can be used somewhere to speed up the backtesting (actually not checking conditions when there is no need to) or to limit the number of trades in one bar in case you got both conditions within a very short period of time.

Windows Vista, 7 and 8 have some strange features that can cause weird effects sometimes. Check here under "In case of problems" to see if you have one of these: http://fxdreema.com/desktop

Those blue blocks pass always, no matter if there were closed trades or not. And this is ok in another setups. Maybe I have to place additional output or just make this one to work only if some trades were really closed... but this can ruin someone's EA without noticing. Now they pass no matter what.

There is a group of pink blocks that is more customizable, but needs more attention and understanding. Read the description of "For each Trade" for more details of how to use these blocks. They can be used to modify SL dynamically.

Also try "Variables". With these things can become even more customized... and complex as well :))

If you remove "Pass" block it will be the same.

Ами ако работи, става. То и това "Variables" дето е залепено от дясно може да се използва за по-сложни сметки, както и някой custom блок. Ето тук съм показал на някой нещо като съм използвал това от дясно, виж в първия блок: http://fxdreema.com/shared/oSr7HQEnb