Posts made by fxDreema

https://fxdreema.com/demo/mt4-crossover-indicators
This is how the crossover in Condition work. It works with 2 candles only, not 3. Yes, try with two blocks

Don's check the checkbox (on the right side of the parameter) while a Constant is used for this parameter. Just uncheck that checkbox... or all of them
https://fxdreema.com/demo/mt4-disable-blocks

https://fxdreema.com/shared/hyvOISJ8e ?

My final statement - what you want is not impossible, sorry

Weird MQL5 issues again... try now

This is only an example, I don't use your settings and I don't even have a Condition block, but I think you want to do something like this - https://fxdreema.com/shared/gXqvNRWrd

"Last loser" - this is NOT the last trade only if it's a loser, this block reaches to the first trade in history that was loser. It can be the first trade, it can be the second... whatever. And if you set it to look at Buys only, it will be the first found Buy trade in the history that is a loser.

Here I wrote about the "close of the same candle" problem - https://fxdreema.com/help/-/working%20w ... e%20closes
In short... don't even try it

I don't understand this "crossing cycle". If you want to do something on each candle after crossover until the next opposite crossover comes, you know, you don't even care about crossovers. If MAx crosses MAy above, then until the next opposite crossover you can be sure that MAx is > MAy. So you can just use > or <

I made those blocks to decide what type of orders to open depending on the open price. If the open price is the the current price, then it will be a trade. The first order is set to be opened at 25 pips from the current price because of the grid size. Ask + 25pips, this is it's open price. But with Price offset you are moving it exactly on the current price (Ask) and that's why it becomes a trade.

The grid size can be negative value, then the orders will be put in the other direction.

It should try 10 times for a given trade, but it depends on the type of the error. It will try to open the rest orders... but when errors start to happen, who knows

The terminal path is where MT4 is installed, something like C:\Program Files\MetaTrader 4.
The data path is where it sends you when you go in "File -> Open Data Folder" in MT4

Again, if you don't use the exact number and data type of input parameters in iCustom, the indicator is not loaded properly and there are lots of error messages in the logs. Try it and you will see. But I will do nothing for your indicator, because as I said - it has nothing to do with MetaTrader 4 itself, this is just another custom indicator made from someone that is not from MetaQuotes. There is no place for non-MetaQuotes indicators in "Condition -> Indicator"

Well, I tried this and here is the result - http://prntscr.com/b1ik54

Maybe there is something specific in your case - weird symbol or some error. In any case, if I don't see the problem I can't fix it

I will eventually add this option in these blocks, if I don't forget I will try tomorrow. Otherwise there is a block "Round numbers detector", but it is to be used on every tick, it detects the new round price when that price actually happens. You can use it to open trades at round number prices.

Yes, a trade can be opened with the pending order if you set it up in a way so the first order's OpenPrice is the current price - Ask for Buys and Bid for Sells. If you want to try it, add fresh "Buy pending orders in grid" and set the Price offset to -25 while keeping the Grid size to 25

It depends. There are multiple ways to store state in the memory and then check it. Variables, Flags, Toggle blocks. All of these are doing the same stuff deep down in the code - setting value in a variable and then reading it's value. Do it in the way you prefer.

Status is this blue text near the spread meter on the chart. What it says can be changed.

Block numbers can also be text values, but use only letters, numbers and/or _. Don't use empty space or non-latin characters.

Here is about EA settings - https://fxdreema.com/demo/mt4-constants

Don't change cross width if you don't understand it.

This is the example about Once per bar and how it can be connected with Condition, it also contains description - https://fxdreema.com/demo/mt4-once-per-bar

Yes, I am already aware of that. This is currently for testing and only available when you open account in their "broker". But it doesn't work in fxDreema at the moment

I can see you are trying something in your profile, but I don't fully understand your rules here. When you make such robot, you must be absolutely specific in each rule. "earlier of the day" means nothing, as well as "previous day resistance" if that resistance is not a specific value.

What I can say... instead of using AND, just connect the blocks one after another. Be careful with those "Close trades" blocks, you don't want to be in a situation when the condition to open a new trade is the same as the condition to close all trades for more than one tick.

Sorry, I have no ideas to put MM methods outside Buy/Sell blocks. In theory you can use the function that is used in Buy/Sell blocks to calculate this value, but I will never recommend to anyone to use the functions I have created. The reason is simple - I will eventually rename/delete them without saying a word. This is the function, use it at your own risk:

DynamicLots("fixedRatio", FixedRatioUnitSize, FixedRatioDelta)

FixedRatioUnitSize and FixedRatioDelta are to be replaced with your numbers

If you replace the file, then you must have 4 input parameters of "color" datatype. Not more, not less, but exactly 4. Otherwise the indicator will not be loaded. And also the buffers must work the same way.

It's interesting that the MQL5 version of HeikenAshi outputs differently for it's buffers. They are O, H, L and C. But in "Condition" I did it in a way to work the same in MQL4 and MQL5

https://fxdreema.com/shared/k4WD8sUW