Posts made by fxDreema

"Formula" block creates global variable named "Result1" in your case. This global variable can be used everywhere because it is global.
But in "Buy now" you can use this option "Dynamic value". And in "on Trade" use "(on trade) Trade/Order under on Trade event" instead of "(in loop)...".

If you talk about your project Global Variables, there you have fixed size 0.1 lot for pending order That formula result is not used.

I think it's ok now. It was something with the latest Chrome.

I think it will be better. I have the newest MT4 and it works faster, not only because function calls are faster. I have to admit that fxDreema generally makes slow EAs because of their structure - some little things are needed sometimes, but when they are not needed they are still there... things like that. Even with this, the same EA is faster in the newest MT4 when it is compiled with the newest compiler.

I don't know about iCustom really, didn't tried it much, but if it does not work they will fix it. Otherwise all the other stuff looks the same. Ok, "Experts" folder is moved to "MQL4/Experts". I expect things to be better, but it will be best if they just let MT4 and MT5 die and do MT6

Often I'm tired of MT4 and MT5 - both have certain problems. And I don't backtest often! But when I do, with all this crappy history data... I can't imagine how you guys do it.

Ти винаги можеш да вземеш нещо от съседния маркет и без да го чертаеш като линия. Е, не и на бектест, но иначе може. Само че нали искаш да засечеш раздалечаване, което съвсем не означава да сравниш две точки от две валути. На мен нещата ми изглеждат по-сложни, като да трябва алгоритъм който да напасне двете криви някак - да работи с всичките им точки, да има допуски, разни параметри...

It looks the same as here: topic/2319
The little problem is that I see everything right on my all browsers
What browser is this, since when it started to happen?

Now instead Constants, Input checkboxes are used. No difference at that point
I think this is better: http://fxdreema.com/shared/zrV0t7UBd
The only points where SL can be modified are BE and TS. If you got "Error: Invalid SL requested" again, put it here. I have made a little update where it will print Ask/Bid price instead open price.

These MM options (% of...) are maybe not useful in every situation. If it is "% of Balance" and the value is 100(%) and Balance is 10000 and the market is EURUSD when 1 lot is 100000, then the lot size will be 0.1.

I think this indicator is loaded, but can't be read or something like that. Is it working otherwise, if you use it manually? Or within another EA somewhere from internet? And after these error messages, will it eventually start to work or they have no end?
How about input parameters, are they ok? - the same parameters count and order, the same datatypes or at least compatible datatypes?

Yes, if it works. But you don't need "Once per tick", ticks are already server by the "on Tick" event and this block "Once per tick" is actually a filter.

Comment section is only one - on the left. This comes from MT4 itself. There is no other available in fxDreema, but maybe I should do this finally.

What about... Once a day -> Counter: Count "n" then pass (with setting 1)

But I don't want to guess what input can I put. I don't know your inputs, I am using those settings from the project, and if you use different... then what do I do? Inspecting something that it's not to be inspected.
Give me something that is easy, fast and straight. Something that will give that error almost immediately. Without conditions and input parameters that can be different for you and me. The only block that can modify SL is obviously the trailing stop block. So what I need is probably 3 blocks -> No trade, Buy now and Trailing stop.

Things are not "now and then", they are always "now". And you can expect that as I can see, because you are using "Once per tick" block, which is actually not needed.
So, when you have conditions like this - one after another - if the first one is not true, the next one will not be checked at all. Let's take "5 MA x> 50 MA" for example - this condition can be true (the block can pass) multiple times in one specific candle, but not all the time after that condition. "5 MA > 200 MA" can, it is always true and the block always passes (if executed) when MA5 is above MA200.

Play with this to see different crossover situations and what is going on: http://fxdreema.com/shared/tpuyHHxdb

http://fxdreema.com/demo/mt4-wrong-closing-rule

As I said above, any block that is on top of other blocks (nothing is connected above, at least one block is connected below) under "on Tick" will be executed on every tick. In other words, you can have multiple groups of blocks ane they all will be executed in the same tick one after another. What will be in these groups of blocks... your choise. It can be Condition -> Buy new trade, it can be Condition -> Close trades.

Can you show me more details? Maybe the name of the block, or part from the MQL4 code that contains this error + some more rows from above and below?

No, these are 30 and 70. There are indicators that have limits like this... well, oscillators, to be correct. For example RSI.

Fixed value -> no units, it's what it is. Dynamic value -> the same story, depends on what is selected, it can be price level or any other level.

It's not to connect N blocks one after another here. See that "on Tick" orange button above? When a new tick comes - blocks 1 is executed. When block 1 is executed and if it passes - block 2 is executed... and so on... Block 4 is executed once when a new trade is created, not on every tick after a new trade is created.

Check this, if this is overcross: topic/2287

I don't know what "overcross" means, but to close trades there is a block named "Close trades" - when it is executed trades will be closed (there are filter settings for this block to close certain group of trades).