Posts made by fxDreema

You are working with >. Try with x>.

But I don't like the way your blocks are connected. Please, take a look at these:
https://fxdreema.com/demo/mt4-wrong-closing-rule
https://fxdreema.com/demo/mt4-once-per-bar

Thank you for that But if you are new, and I always say this to anyone who is new, I think that it's better to work in the demo mode for a while. Knowing that you can't make as many connections as you want will make you think about using less blocks and less connections, which is always preferable There are people with 700+ blocks and honestly, I have no idea how they can work with these giant projects.

I told you, this block counts how many times it runs, how many times it is executed, how many times other block reaches it. There are no minutes, no seconds. If this block is on top level, then it counts ticks.

And how do you know when to pause the EA and what is the correct time?

You can make a shared copy as well. I hope you are not asking me how to send e-mails with attached files

There is no particular field where you can set such information to be embedded to the output EA (but I should add some). Only if you make a custom block you can put such information under "Global variables, includes" and then when the block is used, the information is automatically embedded.

If you do the whole process forward, I mean you detect condition 1 and then Condition 2, then meanwhile you can just increment some Variable while the EA is working. Counting candles is for the case when you somehow detect the previous candle NOW. If this is the case and you somehow know the ID, there is no reason to search for the time of the candle, because you already know its ID. If the ID is 15, then there are 14 candles between candle 0 and candle 15. But with the EA it's kinda tricky to find the ID of a past condition, because the Condition block works in the current time and does not search for past conditions.

There is no time range, this block counts the times it has been reached by other block

I personally can't do webinars, I can only write in english. And I actually don't want.

There is no such time delay block. There is a delay block that stops the whole EA (and MetaTrader freezes) for a while, but this one is more drastic and for small amounts of time. Otherwise this would be the idea: https://fxdreema.com/shared/JOQ3moZce

If you want to detect whether the indicator is red or green, just compare its value of candle X with its value of candle X+1. Obviously if the previous value is lower than the current value, then the current bar is green.

So...

1. You make a pending order with SL and TP
2. The pending order turns into a trade
3. You immediately delete the TP and manage the SL in some way
   ... and you ask how to delete the TP.

What I am asking is - why you are putting this TP in the first place? If TP will always be deleted, why do you need it at all?

I don't see shared copy link here, but I can see your projects anyway. I think you are trying to make something like this: https://fxdreema.com/demo/mt4-buy-sell- ... conditions
Take a look at the examples and notice the settings in the blocks. Also make sure you understand this concept: https://fxdreema.com/demo/mt4-wrong-closing-rule

I was saying this only as an information. The indicator must exists as an .ex4 file in /Indicators of course. Even if you manually write an EA, you don't actually need the indicator contents, you only need the name and the input parameters of the indicator. Indicators work as a separate program, they are not embedded into the EA. The EA only "calls" them, in other words - tells MT4 to load them and get the information from them - and they are automatically loaded and connected with the EA.

If you manually load and indicator to the chart, this is another instance of the indicator, but its data is not used by the EA. The EA deals with indicators automatically.

The file contents looks like this for me:

Time (local);Time (server);Chart;Condicion;Main Line;Signal Line;Column 5;Column 6;Column 7;Column 8;Column 9;Column 10
2016.10.11 21:05;2016.10.11 21:05;EURUSD;Condicion 1;8.28193833;7.96761995;0;0;0;0;0;0
2016.10.11 21:07;2016.10.11 21:07;EURUSD;Condicion 1;67.11864407;70.26376675;0;0;0;0;0;0
2016.10.11 21:08;2016.10.11 21:08;EURUSD;Condicion 1;65.98639456;67.34170092;0;0;0;0;0;0
2016.10.11 21:10;2016.10.11 21:10;EURUSD;Condicion 1;86.83544304;81.64531494;0;0;0;0;0;0

How does it look for you?

It's a shame, but I prefer to keep things simple, mostly because I'm the only one behind all this Also, I never wanted to make desktop products anyway. I was experimenting with the desktop version back then, because someone was not feeling secure about having his projects outside his PC.

There is one thing I like about the desktop version - because it's offline, the server feels better. There are few people who have giant projects with 700 and more blocks But this is not a big problem.

"n" is the count of passes, that "Counts before pass" parameter. I use "n" in the title for better understanding of the thing that the block does. But maybe I am wrong about the better understanding

When the block passes... it will continue to pass again and again. It does not pass few times, then it passes forever (or until you reset it)

The ID for reset have nothing to do with the ID of the blocks. This ID is only for those counter blocks and normally it should be something like 1, or 2, or 3... But again, maybe I was wrong to give this parameter such title

But in the "shared" project there are no blocks with such IDs.

You know, you can give IDs that are not numbers. I will suggest exactly this. It is more convenient to control blocks with IDs who have certain meaning instead of some weird numbers. But better use one word IDs, something simple.

Between two of them... which two? If you know their ID's, just get the difference. If you know their times... the same, with little more calculations.

If I am not wrong, this indicator have 1 output buffer, not 2. I feel that you want to do something like this: https://fxdreema.com/demo/mt4-buy-sell- ... conditions

I don't understand what "activated" means here. Otherwise yes, MetaTrader allows you to get information from any timeframe. Well, there is a little issue with the biggest timeframes when backtesting.

Arrows are not arrows. Indicators have buffers, Buffers are arrays with data - one value per candle. Where you don't see arrow, line or whatever graphical thing, the value is EMPTY_VALUE, which is a constant with value that is the biggest integer number. Otherwise the value is the price value where the graphical element is, let's say 1.23456.

Use the "Trace" block to see what is going on.

"Indicator is visible" passes if the value is different than 0 and EMPTY_VALUE. Sometimes indicators are giving value of 0 instead of EMPTY_VALUE.

"Indicator is visible" is almost identical to "Condition", where you have something like The Indicator > 0. This is because "Condition" does not pass at all if one of its values equals to EMPTY_VALUE.

Only for custom indicators in "Condition" you have extra options in "More settings" - some of them allows you to find the latest "visible" value of the indicator. By "visible" I mean different than EMPTY_VALUE. Try these options.

100 pips per week does not sound like something that can be described with the word "average" to me. Try "Check profit (period of time)" instead. By the way, I forgot the meaning of its parameters, I guess I should think about more descriptions But maybe it would be tricky to set Monday-to-Friday in this particular block. I can also suggest to try Bucket blocks, note that in "Bucket of Closed Trades" you can specify these times in various ways