Good for you!
Posts made by l'andorrà
-
RE: I want this EA to take trades in of the trendposted in Questions & Answers
The problem is defining when a trend is a trend. When is it confirmed? IMHO you could begin with a simple approach and then add more complexity layers later. I would begin with an exponential MA, for example.
-
RE: News during Backtestposted in Questions & Answers
I support the motion. Any help in this field would be highly appreciated.
-
RE: Ichimoku Cloud Breakoutposted in Questions & Answers
This is a good initial approach. In order to get what you want you should use two condition blocks instead of one. The first block should specify where candle 1's close should be (above the cloud) ans a second one telling where the open price should be (below it) for a buy. Then the EA will be more accurate.
-
RE: Simple Problem Needs to Be Solvedposted in General Discussions
Not sure I fully understand what you mean. Do you mean you need to open a buy or a sell as soon as the EA is executed after being removed from the chart?
-
RE: remove expert dal graficoposted in Questions & Answers
@luca-9 You can use this block where appropriate:

-
RE: This EA placing orders but not working properly,,,,WHy,??posted in Questions & Answers
I'm afraid there is not fxDreema function doing it the way you want. You should build a specific structure for that and it would be 'easy' or trivial. On the contrary, it would need time and effort. Sorry for the bad news.

-
RE: IDEA ! Verification and correction Backtests (bad data).posted in Questions & Answers
Sounds like a great idea. I hope you can find someone to make it real.
-
RE: Hieken Ashi Candleposted in Questions & Answers
Sadly HA wicks are not available/selectable in fxDreema blocks.
-
RE: Is the admin modifying the code on variables?posted in Bug Reports
Unfortunately, I'm not a programmer so I have no idea why the block does so. I just can check it did as I described. My guess (and it's just a guess) is that block 5 is correctly executed but the 'For each closed trade' applies that candle 0 condition on what it can find on the 'Account history' tab, ignoring the time gap. That is the best explanation I can provide with my 0 knowledge of mql4 language.
-
RE: Is the admin modifying the code on variables?posted in Bug Reports
@roar I finally found it! I found the damn problem in this structure. After endless tests week after week I can confirm the problem is in the way the ‘For each closed trade’ block filters the conditions connected to it. This is the way I discovered it.
I made some modifications on the initial structure and I added a time filter at the end of the day that closed all trades a few minutes before 23:59:
https://fxdreema.com/shared/pjj8UV5Md
Thanks to roar’s suggested script I soon confirmed that variables were correctly reinitiated at the beginning of the next day so why the closed trades result was always ‘restored’ over and over?
Now please look at block number 5. There I selected today’s session as the only time period to collect information from. How was yesterday’s value been recovered every day if the variable was correctly reinitiated AND the new day has no closed trades whatsoever?
The answer came to me just by chance (kind of). I decided to watch the chart between two trading sessions just to see if I could find any hint to shed light on this issue. And boy I saw it! As soon as the new session was open at 00:05 I confirmed once more on the Expert tab that variables had been correctly reinitiated. However, yesterday’s closed trades result was visible…again! What was different now was that I saw the hour that was supposed to happen on the Expert tab. IT WAS AT 23:05, MY LOCAL TIME!!! There is one hour gap between my broker’s server and my local time. The filter used in block 5 was still considering that it was the previous day and not the next one. All closed trades were recalculated and the variable changed accordingly.
So the problem is that the ‘For each closed trade’ block cannot distinguish correctly broker’s time and local time. As it goes to search for all closed trades on the ‘account history’ tab, the local time is considered only. That also explains why the error disappeared ‘spontaneously’ after some time every day. That happened exactly one hour in the new day, when my local time was 00:00. So much pain and agony for weeks is finally over!
Could the admin finally fix this? I would definitely appreciate.
-
Different pip size rules for same digits chartsposted in Questions & Answers
I'm using a broker using the same digits number for different symbols with different pip size rules. For example, BTCUSD and XAUUSD are both two digits charts. However,
If I do this on the pip size rules:
Only BTCUSD will work correctly because XAUUSD would need a 0.1 value instead of 1 as per the image above. I tried to use this formula recommended some time ago by roar:

But it doesn't work either. I don't know if I'm not using it correctly or if I'm missing something. I know I can type all symbols on the pip size rules window one after the other but that can be very annoying, especially when changing the broker. Is there an easiest way to get it right once and for all?
-
RE: Buttons removing themselves and not functioningposted in Bug Reports
Can you please share the link to the project?
-
RE: how can we calcute highs of x daysposted in Questions & Answers
@mr-lenny You can do it this way for the last 10 days, for example:
