Posts made by fxDreema

Now "Formula" does a simple calculation and puts the result of this calculation in previously created (by you) Variable. This Variable is global for the whole EA and can be used everywhere.

http://prntscr.com/90dmkw

Block IDs matter sometimes! https://fxdreema.com/demo/blocks-execution-order

There is something called Custom Indicators designed to make calculations using the data from candles. It's not that this thing can't be done in an EA, but custom indicators not only give visual representation of calculations, they also know what to calculate and what not to recalculate.

Otherwise the job looks is like this - there is a for loop and inside you check each candle and increment some variables. But fxDreema is not very good when it comes to creating and working with loops. It's easier to write those as MQL4 code.

Try "Condition" like this:

Indicator > Value Numeric 0

Use the proper buffer, but with Candle ID bigger than 0. Indicators who draw arrows most often return EMPTY_VALUE for the current candle (where Candle ID = 0).
Note that in "Condition" if on of both sides equals to EMPTY_VALUE, the block does not pass. That's why it cannot pass if the buffer is EMPTY_VALUE.
After "Condition" you can put "Once per bar".

Another way is to use "Indicator is visible" instead of "Condition". Again, with Candle ID bigger than 0.

Also, there is a block "Indicator appear", which acts a little bit differently than "Condition".

"Turn On" is not the same as "Run"!

As you know, any block can be disabled, which means that it will not be able to run when you run the EA. It still exists in the MQL4 code, but there is unique variable that exists only for this block which is false and because of that the function of that block is not allowed to run. To "Turn On" this block means to set that variable back to true.

To run a block, this means to call it's function in the MQL4 code. Inside that function, the first thing to do is to ask whether the variable (which I explained above) is true or false.

Just look at the code, I think you will get it quicky. Especially with so many blocks that you have, one of the first thing that you will see are those special variables, most of which are = true;

This is not an error. I surrender I tried this project on two other PC's and it still works for me. I have no idea what is unique in your system

"Turn ON" only enables a block by it's number, it does not run any block. There is a block "Run blocks". I sill suggest to give custom IDs of these special blocks. Note that not only numbers, but also latin characters are allowed. This option can also be used: http://prntscr.com/8ziaxb

If you can try this - open Developer Tools on Chrome (Ctrl+Shift+I), then under "Console" do you have some errors when the problem happens?

Or, if you have some extension installed that can somehow interact with that page. What I know is that I also have the latest 46 version of Chrome, other people are also using Chrome, and for now it's only you who see this bug

I have this:
https://fxdreema.com/shared/fDHlfRh8d
http://prntscr.com/8za8pz
It appears for me that when a trade is closed after the block was used, the information is updated.

What if you put this block right before using it's values?

Another way to the same thing is to be able to allow to put some blocks on hold under "on Tick". But I decided that it's better to have a special working field for this feature. Everything is actually very simple if only 1 block can be on hold at a time, it's easy to stop the whole EA until particular block passes. The problems starts when I decide to allow multiple blocks to be on hold at a time, and more than that - to allow chains of blocks to be independent from one another. So, if some group (chain) of blocks is on hold, there could be another group (chain) of blocks that works for itself. Now the things are also becoming aynhronous and probably unpredictable. Even I have hard times thinking in asynchronous mode

In such problems when I just don't have an idea what is going on, I ask for TeamViewer. If you want, we can connect and I can see what happens directly on your desktop.

By the way, this problem happens only in Chrome or also in other browsers?

https://fxdreema.com/shared/zGWM6Ohrb

Ok, I fixed the issue when a trade is meanwhile closed. I'm not sure that this is the better way, maybe someone will want to use the initial count of trades, but because you are reporting this now, let's say that this is the way to do it.

The other thing is a bit harder to make and I'm even more unsure about it. I mean, when a trade from the list is closed, it sounds fair to work with it anymore. But when a list is created at moment A and then at moment B a new trade is created, why should this trade appear in the list? Well, in fact it will appear in the list on the very next tick.

Something is missing here: http://prntscr.com/8z5j0v

Any block that is not connected to another block is simply not included to the final EA Also, it's better if you use some Formula block to connect it somewhere before the other block that will use it's result.

What I can suggest is to look at the situation from the current moment to the past. Start from the last conditions. Something like - if CandleHigh(5min) is lower than the breakout price and CandleHigh(1hour) is above, then "Once per Bar" go to Sell.

I know that it's more human friendly to look at things starting from the oldest moment - this hapens, then this happens, then do that - but in MQL4/MQL5 this is the hardest way to do things. I even created a new working field where the blocks are supposed to work that way (one after another in time), but I used some tricks and the result is too slow, so I decided to not publish this.

Hm, this is interesting. Now I am also wondering if I can add some parameter for this, but there is a chance that I will fail implementing this, because the block is also designed to draw text and there are some issues in MQL4 when we mix numbers with strings or vice versa.

Otherwise there is this function http://docs.mql4.com/convert/doubletostring that obviously turns any floating number into a string with X digits after the point. The thing is that function takes a variable.

The other way is to use this function http://docs.mql4.com/convert/normalizedouble to normalize the value that the indicator is giving to the EA. I would probably do this directly into the indicator itself... if this is a custom indicator of course.

I still don't know why this happens to you. I tried on other machine and it works fine for me. I also don't have other complaints, it looks that there is something rare that causes this and I just have no idea what is it. Operating system, browser, mouse, processor... I can also try with some Linux, who knows what is the cause.

The problem is that pink blocks does not work in this "combined" mode that you want. The first block is called "For each Trade"... just look at it's description. It says "for each", not "load all", this block creates a loop for each available trades and runs the next blocks multiple times. There are also some examples in fxdreema.com/examples.

"check loss" checks the loss of a single trade at a time. Look at this topic, I just answered to a similar question viewtopic.php?f=2&t=3307

Candle ID parameter. 0 is the current candle, 1 is the previous, then 2, 3 and so on. These are positive values and yes, the bigger the number, the more you go to the left on the chart.