Posts made by fxDreema

I personally work in portable mode, but I will try how it works in normal mode now

I have MetaTrader here running with this EA for a while and I didn't noticed problems. I was also switching my PC on and off (Sleep actually, not restart) and here is what I got: http://prntscr.com/cxkywn

Anyway, why don't you try this: http://prntscr.com/cxkx0a Well, set the timeframe to daily as well.

Nooo, look at the white and orange circles on the left side of each input field in the "Variables" panel. If you put this calculation in the left (white) field, it will happen BEFORE the block does its job. That white circle represents the input of the block (which is also white) => the calculation happen in the input, when the block is called. Put the formula on the orange field and then the formula will run AFTER the block does its job, which is to set values to the variables.

mfuetterer, I also see another problem in your screenshot. You have put Variables in the Adjust fields. The result is like this:

Candle_Close = Candle's Close %(#FF0000)[+ Candle_Close]

This %(#FF0000)[+ Candle_Close] is the extra thing added because of the Adjust field. As you might expect, every time you run this block, the value of Candle_Close will increment more and more, because you are actually adding Candle's Close to its value.

I guess I have to make filter block such as "Pending order triggered" or add some option in "Trade created". But if you are using "Trade created", it should not pass if pending order is created. I just tested it and it works as I expected

I put this EA in my demo, but who knows when will I see trades and errors. Do you have some logs?

MetaQuotes sometimes change their format and older .ex4 files can't work anymore, but now I don't think that this is the problem now. On the server I use compilers that are month or two old and everything works on my MetaTrader build 1012. Note that there are many other people working with fxDreema every day as well. Even the desktop version, which is from 2015 still works for me

You can connect the gray output with the input, but is this a good idea... Why do you have so many off quotes?

You can have trades closed years ago. Who cares about these long forgotten trades. You want to work with relatively new trades and the first time sets the oldest trade possible. For example, you may want to select only trades closed in the past 5 days, not anything older than that.

I made this block because many people wanted to know what was the profit of the current day. How can you know this... by looking at all the trades existed after 0:00 of the current day.

Once per bar only prevents the next block in the chain to run on every tick. Instead, it runs maximum one time for each bar. This block has no opinion about the work of any other block, it just limits their execution.

miro1360 already said that, use "Once per bar"

Are there error messages in the logs?

candle close - this thing is not detected. I tried to explain the problem here: https://fxdreema.com/help/-/working%20w ... e%20closes

Well, I don't use OrderSend() or OrderModify() directly. There is a big function that does some checks before and after trading. In case of failure, the EA should try again few more times (10 in total) and then will fail, which means that the gray output of the block will be active. But there are recoverable errors and fatal errors. In case of fatal error, there will be no retries. ERR_OFF_QUOTES is from the recoverable errors, so it will try 10 times with 1 second delay between each attempt.

You know, I explain arrow indicators so often, that now I really hate to do it Search for EMPTY_VALUE in the forum and probably you will find some of these explanations.
Unfortunately there is no built-in custom indicator (in /Indicators) that puts arrows and works as regular custom-made arrow indicators. I wanted to make and example and put it in "Examples", but what can I do. Yes, I can find some custom indicator and do it with it, but then the person who will see that example will not have this indicator installed, and I prefer all examples to be ready for testing.

Yes, I renamed "Indicator tester" to "Trace". I also updated it a little bit, so now it outputs prettier information. You can always use "Trace" on the server for testing indicators, no problem at all.

Hint: For arrow indicators, if they don't work, try with Candle ID bigger than 0

When you have x>, this means that the Condition block does 2 checks - one > for the current candle and another < for the previous candle. More info here: https://fxdreema.com/demo/mt4-crossover-indicators This means that the x> state... I mean the time period where both checks are true... can be up to 1 candle long. When that candle is closed, this x> is no more true. While if you use >, this remains true for all candles where one of the lines is above the other, until they cross.

But because x> remains true for multiple ticks (while the current exists), "Once per bar" is used to catch only the first one.

If you have 2 blocks with different indicators connected one after another and if x> (or x<) is used, then better don't expect both crossovers to happen at the same candle. Instead, leave x> (or x<) only in one Condition and in the other use > or <. You know, if now MAx is > than MAy, this means that MAx crossed MAy some time ago.

There is another kind of crossover as well - https://fxdreema.com/demo/mt4-price-vs-indicator

This is job for some indicator

Refreshrates orders?

To be honest, I don't understand Excel very well. I don't even know how to open this .csv file with it. But I'm sure that Excel has many different ways to format the data, so I guess this is what is going on

I'm aware about this problem in the desktop version, but I stopped making desktop versions year ago. Since then I rewrote everything from PHP to NodeJS and I will update everything on the server probably after few days. In other words, PHP is history, as well as the current desktop version. I of course tried to find why this problem appears back then, without success. I used ExeOutput for PHP to make it, and this software is not only buggy, but also unsupported.

Ok, I posted an example above. There is no 1 block to do that at this time, but with a Variable it can be done. Download the project as .mq4, import it into your projects and you will see how it's done... and build on top of it