Posts made by fxDreema

Martingale in ONLY for the lot sizes, it has nothing to do with the price. And because it's just a betting system, normally it should be used only with 1 trade at a time, but most people are using it to add more and more lots on loss.

Here is one example for how to add more lots: https://fxdreema.com/demo/mt4-loop-add-to-volume-on-loss What is interesting here is that each next trade is a "child" of the first "parent" trade and automatically shares some properties with that parent, like SL and TP. I guess that this is what you want - the same SL and TP. They can also be modified with "modify stops" even before "add to volume".

Well, the objects have specific names (mml0, mml1... mml12), so there is no need to search for them with "For each Object", they can be accesses in the Condition block by their name directly

Could be some bug. Try with reloading the page. Which Close button doesn't work?

Show something from what you did. There is a big chance that there is some mistake in what you did, but no we can't guess what it is

This is my idea for detecting the real first day and last day of the month: https://fxdreema.com/shared/iB1YvWgSb
The first pair of blocks would print yellow arrows on each candle in the first day. the second pair prints pink arrows on the last day.

For newbies, && means AND and || means OR. The whole formula can be written in 1 row only, but I wrote it like this. The condition is asking whether the first row OR the second row is true.

Let's take block 1 for example, the second row:

TimeDay(TimeCurrent()) < TimeDay(TimeCurrent() - 86400)

TimeCurrent() gives us the current time of the current candle. This is the server time, not the local time on the PC. This is the number of seconds since 1.1.1970.
By the way there is also function Day() that can replace TimeDay(TimeCurrent()) .
86400 is the number of seconds in 1 day.
TimeDay gives us the current day. Today is 25 for example.
TimeCurrent() - 86400 is 24 hours in the past, so TimeDay(TimeCurrent() - 86400) gives us the day of yesterday. For example 24.
So, what I ask is whether the date today is < the date yesterday. If today is 1 and yesterday is 31 (or 30, or 29), then I detected the first day of the month.

The first row:

DayOfWeek() == 1 && TimeDay(TimeCurrent()) < TimeDay(TimeCurrent() - (3 * 86400))

DayOfWeek() is the day of the week, where 0 would be Sunday, 1 is Monday.... and 6 is Saturday. So DayOfWeek() == 1 asks if the day is Monday.
The problem is that Monday is not always day 1. Maybe Monday is 3rd. So I compare the Monday's day with last Friday's day.

It's all pretty much the same in block 3, but the opposite.

I think that this was my idea when I made this block - to put that parameter to Custom Price Level and then for SL and TP to select Custom Price Level as well. When SL and TP are set to Custom Price Level, the "Price relative to" option is useless anyway, so that third option was only there to say that SL and TP are custom levels. It's a little bit confusing, I know. But I now added the "missing" parameter, you can try it.

There is one block to measure distance, type "distance" in the search input

You are asking for a custom indicator, this is not something that EAs do

Is the ID in each Pass once block different? Which project is this in your projects?

Yes, it's Average, not Weighted. I don't know, I never added such thing in any block. Maybe with a custom code. To be honest, I don't really know what is weighted average

You can manually add it. Here is more info: https://fxdreema.com/tutorial/builder/indicators#11

What is this in "on Trade". All the blocks used there are from those filtering blocks that are supposed to be used there only to detect which kind of "Trade" event happened. But when you detect certain event you should do something, for example to use "Delete pending orders" after "Trade closed" (by TP for "Closed by" property)

The indicator is suspicious. I guess that it loads again and again, you can see that in the logs. Check if its input parameters are correct again.

As roar posted above, you can store values in these Variables. Variables are exactly that - pointers to certain address in the memory

Here is this topic we discussed this problem: https://fxdreema.com/forum/topic/6231/two-conditions-are-met/10

Yes, better post some example (Projects -> Create a Shared Copy). I can also see your projects, so for me only the name of the project works. Otherwise different timeframes should work for the Tester.

There are some help materials, look at Tutorial, Examples and also in the EA builder itself there is info for some blocks and even their properties. I agree that the help materials are not very good, but I personally have problems making them. I don't know, I just can explain something much better here for example, where it doesn't have to be super serious. So if you have some particular problem, ask.

Well, you can always create global variables from Variables panel. Then there is a block for custom MQL code (the last one in the list). To use the variables, simply write their name where it's needed. Or, some calculations can be made directly in the input fields of all blocks... depending on how simple the calculation is. In all input fields you can write MQL code. Well, it's a little bit different for "string" inputs, but still MQL is possible.

I don't have videos. But what do you mean, where do you want to add them, or is the problem that you can't find out how to place certain type of arrow?

How many lines does this indicator create? Because these "For each Object" blocks are supposed to pass for each object that is found, and in them you search for horizontal line. That "Arrow type" that appears is some visual bug, don't look at it So if you have 20 horizontal lines, expect 40 or more pending orders.