Posts made by fxDreema

When you work with %, it's very easy to break things, because % is something relative. I need more information about that problem

Try "pips away from open-price"

It's added already, search for "Apply Template"

"Condition" where you have this: Indicator > Value (0)
Buffer 2 is for the blue arrow, buffer 3 is for the red one. Important, set Candle ID to at least 1.
http://prntscr.com/7jhd9e
http://i.imgur.com/jx3VKa1.png

This appears to be the function to do that. It does not exist in a block, but I can add it

I did that. Thank you for noticing this bug in the code

Maybe the problem is here: http://prntscr.com/7j040o
This long option helps for another possible problem actually, but sometimes it's not needed, it depends.

These are examples that can be tested, each of them contain small description and they cover the very basics: https://fxdreema.com/examples
There is something more here: https://fxdreema.com/documentation/

Some picture maybe?

There is a block named "Comment" that does something very cool. It prints information on the chart and then the information stays there. The last state of it stays on the chart. Also, you can put multiple "Comment" blocks and make each of them to print it's own information at different place on the chart

Like this? http://prntscr.com/7ik1x6

I think you need to understand some basics like this one here: https://fxdreema.com/demo/mt4-wrong-closing-rule

Such value is not collected, but with some Variable, why not.

Martingale asks for the lot size of the last trade, no matter if it was Buy or Sell. But you can separate them if you use different group number, because it checks this parameter

If these lines have different nature (values) and you can see them crossing only because they are printed in the same window... I don't know how

I don't know, it depends

There is a MQL4/MQL5 function called NormalizeDouble. Most of the time you can work with these values, only sometimes they need to be normalized. Why... I don't know really, this is some thing in C++ that I still don't understand.

Do you have problems if you use it that way?

Yes. "Once per bar" means this: I am a block and I can pass if you run me, but not more than 1 time while I am in the same candle. Try me on the first tick - I will pass. Try me in the middle of the candle - I will pass. But only once.

What synchronization?

The problem is probably here: http://prntscr.com/7i2bn0

The thing is, these blocks are still under "on Tick" so they depend on the ticks flow as you can imagine. You have 1 minute time window to react, but if there is not a single tick in this time period, there will be no chance for block 8 to run that day. You can also have connection problems at that time, who knows. So I will suggest to extend this time a little bit, just in case.

Or you can put any calculation using native MQL4 functions here: http://prntscr.com/7hkq7t
Because not everything in MQL4 is hard to do. For example, the Ask price can be get by simply writing Ask. Ask is predefined variable. Also Bid.
http://docs.mql4.com/predefined/ask
Some account data is also easy, for example AccountBalance() is giving us the current balance: http://docs.mql4.com/account/accountbalance

__
The question is: If conditions below "once per bar" are met after the second "zero" of a candle, does the EA pass when the condition are met or not ?
[/quote:2pl3363t]
No. A block runs only if the one above passes. The block on the top runs depending on the event where it is placed. Under "on Tick" it like you have a block "On Every Tick" above all "first" blocks.

I have ideas to add a new workplace where things will be different, serial, if I can use this word. Many people are actually expecting things to be like that. If "Once per bar" passes to some "Condition", to stay on that "Condition" until it passes. It's not like that at the moment. Under "on Tick" everything is fresh when a new tick comes, blocks on the top run once, and those below them... depends.