Posts made by trooper

Cool thanks. I´ll try it now.

Hi

I´m working on an EA that draws arrows when there is a signal. Arrow up below de low of the candle for buy and arrow down above the high of the candle for sell. The arrow up is showing bellow the candles as expected but the arrow down shows on top of the candles even when I select candle high.

Here is an example of what I did.

https://fxdreema.com/shared/wkNo5utcc

Please help.

Hi

Is there a way to make a condition that counts in the last x number of candles y number of candles were bulls? For example, if I want to check if in the last 5 candles 3 or more were bulls?

Thanks

Hi

I have read all the documentation and have a doubt about the blocks number sequence. Do the number of the blocks have to be always in a sequence like 1,2,3,4,5...10? If I need to change the order of the blocks like I need to move block 4 before block 3 as in 1,2,4,3,5...10. Does that creates a problem with the running of the EA? Do I need to delete all the blocks after block 2 and recreate the sequence again? Can I have the blocks numbered in any way like 2,1,5,3,4....10? What is the correct way to edit the sequence of the blocks without having to redo them all over again?

Thanks

OK I´m going to test it now and we´ll see how it works. Thanks.

Oh no, that is not the one I´m refering to. I did corrected the one you mentioned.

The one I´m testing is an earlier version that I´m running on a demo account, works correctly and the settings are actually correct with Trailing Step set as is meant to be. But the problem still exists. The TP is set to 0 when the trailing stop is moved when the price is at or too close to the TP.

__You have trailing stop with Step = the size of TP. This is weird [/quote:3q3a8mv3]

Didn´t understand what you meant by that!!!

__I don't remember why, but I have set it in a way, so if the desired TP level is equal to Ask, TP to be set to 0.[/quote:3q3a8mv3]

That is what I see happening. The TP is set to zero when the Ask (or Bid) is equal or too close to TP. Then the operation has to be closed manually otherwise will be closed when it hits SL even if already reached the original TP. Is there a solution for this?

Hi

Hope you can help me. I´m having a problem with the trailing stop on a MT5 EA. That happens when trailing stop tries to move the SL when the price is too close to the TP level. As there is a minimum distance limitation on where the TP can be placed, even though only the SL was changed, that causes the TP to be deleted leaving the trade without a TP. Is there a way to solve this? Is there a way to only change the SL without affecting the TP?

Thanks

I´m sorry you are completelly wright.
I just realised what you meant by the lowercase. Yes when I set the type as bool and the value as false (lowercase) it does updates as bool and doesn´t change to string.

Thank you.

Hi

Yes I know the EA works fine but the Constant type is string when it should be bool. When you go to configure the parameters of the EA on the chart you have to type true or false instead of selecting it from a drop down menu. I haven´t tried it but I assume you can´t optimize it that way either. Anyway I changed the constant type manually on the mq5 file on the Metaeditor and now it works as it should.

It would be nice though to be able to choose bool type on the fxDreema Constant (input).

Thanks

Hi

Another small issue I found.

I´m trying to create a Constant (input) as a boolean type to choose to use or not trailing stop. When I enter bool on the type and click Update, it changes the type to string. Still works that way but the problem is that on the EA parameters you have to write True or False instead o selecting it from a drop down menu. Could you please have a look at that?

Thanks

OK agree. Thank you for that.

Yes you wright. I thought I should use it in minutes as in 60 but the correct is PERIOD_H1.

Now is compiling fine. Are you going to leave like this?

Thank you very much.

Hmmm. I can now add the type as ENUM_TIMEFRAMES by writing it. However it seems that created some other problems.
Now the type is not drop down anymore and it creates other error messages when I try to compile it that we didn´t have before.

Please check it again.

I´m glad you understood what I meant.
Really enjoying using fxDreema. Great tool.

Will wait for your solution.

Regards

Thanks for your answer.

I did see reference to the constant ENUM_TIMEFRAMES that you mentioned and cannot be set as an option in the Constant type.
Like I said before I did try as integer with different values and it always show the error message when I try to compile it. You can see that in the exampe I posted in my fist post.

So if I understood wright you say that we cannot use the timeframe constant in fxDreema at the moment?
Is that somethng that it will be implemented soon?

Thanks

Hi guys

I´m new to fxDreema and having a little problem trying to create a timeframe constant (input) in MT5. I did some search but couldn´t find an answer.
I tried to set it as text and integer, with diferent display names, and with different values like 60 (in minutes) or H1 (as it appears on the chart in periodicity) or PERIOD_H1. Every way I try I get an error message when I try to compile and generate the ex5 file.
The message says:

'MyTimeframe' - cannot convert enum variable 'w' not used

This is an example where I set the MAs timeframes with the constant.

https://fxdreema.com/shared/8GCBtLald

I would appreciate your help