Posts made by fxDreema

@implosion You can try to logically block the ticks with these Terminal Variables (called Global Variables in MetaTrader) - https://fxdreema.com/help/working-with/terminal-variables. This is how you can send information from one EA to another.

I wrote in an email. In one block you are checking whether Trix is < 0, but this indicator is some kind of Moving Average and it doesn't have values lower than 0. Or at least this is what I see when I add the indicator on my chart.

Interesting idea when the block doesn't work for pending orders. I will think about it. But I think you can do that today if you want. I guess there are 2 ways - to add new pending order or to close the old one and replace it with another. While you are in the loop (For each Pending Order), you can use the attributes of the currently loaded order (OpenPrice, SL, TP...) and make another one with the same attributes.

If it's only for 1 single trade, the last one, then you can use:

For each Closed Trade (set 1 to Not more than....) -> pips away from open-price

I'm not against people showing their products in the forums, especially after I did that when I started this website But I also don't like spam and I hope I will not see his posts in every other topic here

The "average" option collects the spread for each tick in the past few seconds and then average value is calculated. I checked the code for this block these days and I think it works correctly.

The Adjust parameter... I forgot the reason why I added it, to be honest. I think the default value for this should be 0. Back then I added this "average" option because of one user who wanted something like that.

If there is an indicator for this, it might be better option

I actually made this and I have it working on my local system. I'm preparing for an update now, I want to upload everything at once, as I usually do. By the way I'm also preparing to move the website to another VPS and I will try to make it with less downtime.

If it doesn't work with one pair of "pips-away - close partially" block, you can try few pairs. Imagine few "pips away" blocks where each one is connected from the yellow output of the previous one. And the first one has the biggest value in it.

Making pending orders in "on Trade" should work, there is no reason for this to not work. But always use those purple blocks to filter the exact kind of event. What you now have in "on Trade" is a little bit no-no. Better do that "Trade Closed -> ....". If you want to see what actually happens, test it in visual mode. But I think that canceled orders are reported in the logs, you should see them.

Will this work in "on Tick"? No trade (buys only) -> Delete pending orders. I'm not sure when do you want to delete all orders. If you want to delete them when there are 0 trades, then just go No trade -> Delete pending orders

In Condition search in Account for Balance and Equity. You can compare these. Or you can also work with this block - Check profit (unrealized) - which returns the profit made from a group of trades, not the global profit of the account.

If the indicator is not installed correctly, you should see error messages about that in the logs. But those 0 values could be the actual values that the indicator is giving.

Yes, it very much depends. There is a block Check profit (last closed). Also, the "on Trade" event can be used. Or another way.

I would say:
For each Trade -> pips away from open-price

People always forget this "For each Trade"

It's one thing to say "I can't compile", but the possible problems are few. There is not only one answer to this. I need more details in order to say what the problem is

For the time of this topic, maybe I restarted the server or something. If this is the case, then the whole website would not work

But the trades does not depend on the charts. Let's say you are using "No trade" block to check whether there is any trade at the moment. For this block you have Group, Symbol and Type options. The Group is pretty much the magic number, which you should understand how it works. So this block asks for these things that are attributes of the trade itself.

And you can change all these options. You can also set the magic number of each EA (it's the MagicStart input parameter). It's all depending on which trades you want to control from the particular chart.

What the chart itself does to the EA is to feed the EA with ticks from its Symbol and also to set the "current" symbol to whatever the symbol is. By Symbol I also mean "Market"... if you see "Market" in some blocks.

Take a look at the documentation about NormalizeDouble - https://www.mql5.com/en/docs/convert/normalizedouble

What they say is this:

Please note that when output to Journal using the Print() function, a normalized number may contain a greater number of decimal places than you expect.

There is no guarantee about these numbers. I tried everything, but still sometimes numbers appear long, even after NormalizeDouble or DoubleToString.

Fixed

Well, I can't test your accounts. Maybe you can tell me something more specific, like what is the difference between these sizes? Is there something interesting in the logs? Also take a look at the input parameters of the EA in case you are using Constants or those checkboxes in the blocks.

I think no. I eventually decided to make the code of all MQL4 and MQL5 blocks the same and meanwhile I fixed some things here and there, but I think I didn't touched the virtual stops yet.

I don't know how secure that is, but you can try this:

In this block you load a custom indicator and you choose one buffer. I don't care what the indicator is and what is the number of the buffer, this block does the same. It expects the values of the buffer to be EMPTY_VALUE or 0 most of the time, and only from time to time to be something different, lets's say the price value.

The idea is that every buffer has as many values as many candles there are on the chart. If each value is a positive number that can be seen on the chart, then you see something like MA line. But some indicators don't want to draw continuous line, so they use that EMPTY_VALUE value, which is a MQL constant that represents the biggest possible integer value.

"Indicator appear" checks the indicator every time it runs and remembers its last checked values. If the last checked value was EMPTY_VALUE and the current value is say 1.2345, it passes.

I also set it to work with value 0, because some indicators use 0 instead of EMPTY_VALUE.