Posts made by fxDreema

What are those conditions?

This indicator has one output buffer, but the value in it is always EMPTY_VALUE. It creates objects, two of which are named UpPer1 and DnPer1. They show the % numbers and they contain string data, this is the description property of the object. I tried this:

https://fxdreema.com/shared/Ovk2BHvT

I tried "Trace" first and it outputs the values, but without " %". The Trace block is designed to show numeric data, so I guess that MQL4 somehow converts the string into numeric, and it does that properly. To be sure, I added Condition block to check whether UpPer1 is > 50 and print Comment message on the right side of the screen. So, this Comment message should only show values > than 50. It actually shows the value with the % thing. But the important thing is that the Condition block works.

When the EA works live, there are 2 sources of time - the server (the broker) and your local time. Depending on where you are or how accurate your clock is, these times can be different. When testing, everything is simulated, including the time. There is no server, even your local clock doesn't matter. The time comes from the candles data, so even if you change this option, it should not change the result of the test.

You use some custom indicator?

Don't do hedging. Hedging is stupid. Hedging is not magical and it doesn't help. Hedging is the worse strategy ever. Hedging only creates problems that are not necessary.

Try "For each Trade -> check age -> modify stops". Also "once per trade/order" can be put to prevent multiple modifications. The thing here is that "check age" works with the age of the trade and it doesn't care about candles, but I think this should be ok. Well, if you want to modify stops on the new candle exactly, then put "Once per bar" above and with "check age" you can check the opposite - whether the trade is younger than whatever minutes.

Works good for me. Why is that 8 pips... it's some minimum size for the candle, you probably don't want to put orders after a doji candle.

I think the best in this case is what josecortesllobat explained above. There are basically 2 ways to do such thing - starting from the current candle to look in the past candles and detect the signal, or while the EA is running to wait for each signal to happen (and use variables to store the current state). I generally prefer the first method when it's easy enough to use it, and it can be used in some custom indicator, but I don't think that it's a good idea in the EA.

By the way, here is another interesting method: https://fxdreema.com/demo/mt4-wait-crossovers But I don't think that this can be used for your case.

Try this: https://fxdreema.com/shared/nDHEjiQzb
I used one "double" variable called Range:

Try this code for the indicator. I didn't checked how it works, I only blindly fixed the MQL errors
0_1554738871057_dailylinesboxes.mq4

I don't know really, it works for me. otherwise error 4802 means "Indicator cannot be created", which... I'm not sure what it means. But MQL5 is often weird. Can you load another indicator?

When you have variables, you can modify them as you want. You set the variable for the first condition to "true" when the condition is true, then the variable remains "true" until you set it to "false", which can be at any time.

But always try to think, is it even needed to do this stuff. Because you can just check 2 condition at the same time:
1 - Is the current price below MA
2 - Is oscillator above level X

Depends on the first condition. You don't say exactly what it is, so for me it looks like it is: Price crosses MA. But you know, if at the current moment Price is < MA, this means that some candles ago the price crossed MA. The question is, do you even care when that happened...

I don't have easy solution for this. I think that custom code needs to be written

This indicator can be found in Indicators folder, but it's not built in MetaTrader. However, in fxDreema you can find it in Indicators (in Condition). If you try to upload the .mq4 file in fxDreema and use it, you will see that it's not that easy, because the buffers return some tricky data. That's why I added one layer of settings to the indicator and added it in Condition -> Indicators. I think it's much easier to work with it from there, instead of importing the indicator.

Take a look at this block called "Indicator moves within limits". It's a little bit crazy block, but I feel that you can use it for something. What it does is what these beautiful horizontal rows of blocks in your project do, but in one single block.

Take profit is hit? Which take profit? I don't really understand what it needs to be done.

By the way, blocks 18 and 19 are not correct in the project above, they would not do what you imagine, they are not to be used with Bucket blocks.

Mmm, what?

Uuuum, what? Pending orders are triggered on the broker side. It's enough to place it. Then you can remove the EA, close MetaTrader, turn down the PC and even cut the electricity cables, the order will be triggered by the broker when the price reaches it. In the Tester of course pending orders are triggered virtually by MetaTrader itself, but still, they should be triggered when the price goes to their open price. Of course, it matters which price - Ask or Bid.

If there is some indicator to collect data about these meetings... Or if you know the hours. If you detect the price movements, it could be too late

I will suggest to put some Trace block to see if the values you are extracting from the chart are correct