Could you please share it again for us to take a look?

He meant something like this.

https://fxdreema.com/shared/fF0cLDGHb

I haven't tested and it's not exactly what he suggested, but it should work.

@roar Ok. Thank you very much for the explanation 😉

@aleximart Hi, take a look at this example

https://fxdreema.com/examples

0_1567791852339_wwww.JPG

@sebabahn I think that could help you. Try to find the string and get the result... https://www.mql5.com/en/docs/strings/stringfind

search for "[is_license_valid] =>". Something like this:

StringFind(
YOURstring, // string in which search is made
"[is_license_valid] =>", // what you want to find
0 // from what position search starts
);

... and then you can use a StringSubstr to extract the result. Not so elegant but, considering the mql language limitations...

StringSubstr(
YOURstring, // string
start_pos, // position to start with from your code above (StringFind)
length=-1 // length of extracted string considering "[is_license_valid] =>" length
);

@trader-philipps Yeah, I've talked to other people that also uses my current Broker (or any Broker in Brazil) and it seems it is a common problem.

Unfortunately there's nothing I can do, like changing brokers... all I wanted was a way to cancel the trade if it took too long to be executed, but I don't think that's possible 😞

@ahaziz1958 In addition to @paragorundu approach you can right-klick on the order list and mark comments as selected. Hence another column will be shown displaying your comments.

0_1567776427632_aae2c449-22e7-4259-864d-0180382c9862-image.png

There should be no problem to do it as a custom indicator. Upload the .mq4 version instead of ex4 whenever possible.

That's hardcore coding for me. Is there any programmer here?

@keshb96 That's correct! The constants will always show up in mt4.
Personally I never use the tickboxes, they only mess things up.

Got it. Thank you!!

@hanssolow double click on the alert you will see

@gunji80 to prevent it from taking trades on fakeouts you can try changing the the level 0 to a more suitable level , but you will need some testing for that

Hi @money123456 , see the NNFX template thread for the JMA with ATR indicator. However, I'm also thinking about the right way to use fxdreema blocks for the condition.

Usually I'd expected to check closed price of candle ID1 if it is X> JMA value (for long trade). However, I think fxdreema works here a bit different with that condition.

I found this example on EURAUD daily chart.
0_1567536341863_Auswahl_510.png

Candle (1) candle closed under JMA line .. that's okay. Candle (2) opened with a gap and hence fxdreema wouldn't find a valid condition. And finally for fxdreema logic candle (3) would give a valid long signal (ignore ATR linits here).
The candle (3) opened above JMA line and closed above. But the low was below indicator line. I observed that fxdreema would if checked for condition closed price x> JMA value give a valid long signal.

Hence I think that for checking the condition "closed above" intends that the open was below the indicator! Do you agree?
Finally I have no clue yet, how to deal with the gap between candle 1 close and candle 2 open. Uusally I'd expect it to be a valid "closed above" by NNFX meanings. What do you think?

Open what?

Additionally, on block 2 you should specify the same candle ID for both left and right operand. Now they are different.

@l-andorrà thanks i solved it but on sell only condition its working fine selling once only when bear condition but the same way buy only not working its setting buy order on all bars when its bull condition i think the problem exists in the coding i tried to delete everything and start over to avoid repeating the problem but its still there i wont give up i'll try again thanks for the tips and advice 🙂

@zackry
In tester mode I can see in journal mode that things look to be going great as it is trying to signal the conditions are met for the trade, but tester doesn't allow sound and I am not getting any phone notifications. I am planning to run in live markets to see if the signals are notifying conditions met and how often.

I join to that petition. Could you please update your example, miro?