Retrieving internal value of a specific counter (ID) in order to put it into another condition

[robotdeforex]

Hello @fxDreema

Is there a way, to retrieve the value of a counter, in order to do another condition depending on that value?

Could you add this funcionality?

Now I´m creating a parallel variable, that I keep adding "+1" in Adjust and using that parallel variable for checking other conditions, but it is not a clean, elegant way.

I hope I was clear in what I mean. What I need to know is if a certain counter (ID = 2) has which counter value: 1,2,3,4,5, etc... in order to use that value for ANOTHER condition with the condition block.

Thanks in advance!

[fxDreema]

But incrementing a variable is not that ugly, I can say that it's pretty much the same story. I made those counter blocks before the variables. If I created the variables first, maybe the counter blocks would not exist.

However, I see something in your project that I don't like:

It looks to me that the variable will be set to 2 every time (1 + 1).

[robotdeforex]

You were right, corrected, hadn´t seen that one!


Anyway I insist it would be very CLEAN to be able to retrieve counter values at some points into some blocks, saves duplicating logic, see what I mean?

Best regards and thumps up for the great job you are doing with FXDreema!

[robotdeforex]

It could be done with another "clear Green" block, such as Retrieving value of Counter, or may be you find another elegant way to solve this. I understand adding another type of variables is not clean, you may find a way to do that, as it is typical to count so many candles, or wait so many candles for a condition to happen, typical for trend systems, also breakout systems, but not only.

Hope you see my point and thanks for having found that MEGA BUG in our bot!!

[fxDreema]

So you wait many candles for a condition to happen. I know this is easier to imagine, we just see things better like this "wait for something to happen and then do this". But we already have candles in the past, so normally (and if possible) the EA should look at the past candles. I mean, why counting something every candle while waiting for a condition, when you can detect the condition at the present moment and count the candles in the past.

But it depends what you actually want to do, because in the EA builder it's sometimes easier to increment variables. There are not many blocks who can look at the past multiple candles and extract some signal out of them.