Posts made by tcanuto

Already tried add in Constants (input):
Type: string Name: Text: info (for example) Value: Enter text here

Already tried?

Wow! Thank you very much! I did not expect so much!

Well, at least as far as possible I have indicated your tool to everyone I know.

Olá Evandro. Tudo bem? Pelo menos mais 1 que fala português aqui no fórum do fxDreema.
Para ser respondido, recomendo fazer as perguntas em inglês, pelo menos traduzido do Google Tradutor.

Em relação a esta estratégia de Hedge, eu já havia tentando, mas hoje não vejo muito vantagem por ser complexo e precisar de mais margem e custo operacional em pelo menos o dobro para ser utilizada. Mas... que acredito que pode ser útil, caso funcione a longo prazo.

Bom... eu tenho este modelo de projeto, caso lhe ajude: shared/4f5nGjCvd

Até mais!

@fxDreema , Friend, I must say that I lost 7 days with this and another previous problem.

I realized it's the same mistake as before.
https://fxdreema.com/forum/topic/4808/compilation-errors

It happened after I added the blocks Check type (last winner)

shared/ubx1M9Job

I hope one day this problem will be solved in the block code.

@fxDreema , I discovered that the problem is in the loop blocks. When I turn them off, it works again normally.

So ... I figured out what this doing is failing can be these looping blocks. I'm going to do some more tests here.

Hello Miro

So ... it happens that before the MT5 update, it worked without crashes, even these blocks, that use based on the example here: https://fxdreema.com/examples

Friend @fxDreema Please kindly test on an MT5 platform for yourself to see the lock on the Estrategy Tester.

Just these errors when compiling:

'Teste HL v1.3.mq5' Teste HL v1.3.mq5 1 1
possible loss of data due to type conversion Teste HL v1.3.mq5 696 31
possible loss of data due to type conversion Teste HL v1.3.mq5 2173 46
possible loss of data due to type conversion Teste HL v1.3.mq5 2974 46
possible loss of data due to type conversion Teste HL v1.3.mq5 3031 46
possible loss of data due to type conversion Teste HL v1.3.mq5 3088 46
possible loss of data due to type conversion Teste HL v1.3.mq5 3145 46
possible loss of data due to type conversion Teste HL v1.3.mq5 3233 31
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 3588 68
possible loss of data due to type conversion Teste HL v1.3.mq5 5240 38
possible loss of data due to type conversion Teste HL v1.3.mq5 5401 46
possible loss of data due to type conversion Teste HL v1.3.mq5 5456 46
possible loss of data due to type conversion Teste HL v1.3.mq5 5584 31
possible loss of data due to type conversion Teste HL v1.3.mq5 5973 31
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 9093 11
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 9093 30
implicit enum conversion Teste HL v1.3.mq5 11419 32
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 11708 22
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 11708 40
implicit conversion from 'number' to 'string' Teste HL v1.3.mq5 11708 59
0 error(s), 19 warning(s), compile time: 15343 msec

Well ... at least until before the MT5 update I had no problems with the tests.

Friend @fxDreema, time is money! I'm still waiting so I can continue my work.

@roar said in Re: Testing pass stopped due to a critical error in the EA:

Check the mt5 journal tab, it should tell which line of the code fails. Then find the corresponding fxdreema block with the metaeditor

No visible error in log files

Re: Testing pass stopped due to a critical error in the EA

It seems like I'm having this problem today. After I compiled my project, and after the MT5 have upgraded build 1629, my EA stops unexpectedly in the first position.

I reviewed the parameters of the blocks of my project and nothing wrong, at least so far.

shared/3ROCuUIzd

I also think, but it still has not worked properly.
In a 3 lots position, this closing partial 66% instead of 33% in 100% pips away. In this case it should close only 1 contract, leaving 2 contracts open.

@tcanuto said in partial close:

How to Close Two Partials?

The first 100% pips away from SL
The second 200% pips away from SL

And this way?

How to Close Two Partials?

The first 100% pips away from SL
The second 200% pips away from SL

@fxDreema It is with Custom Price level - Candle - Parameter Candle High or Low - Candle ID 1, which means SL in the minimum or maximum of the previous candle.

It is with Custom Price level - Candle - Parameter Candle High or Low - Candle ID 1, which means SL in the minimum or maximum of the previous candle.