@vhager maybe some pairs dont have data from 2020/01/01, their history starts some time later?
@l-andorrà the formula is correct, otherwise there wouldn't be any prints at all
@vhager maybe some pairs dont have data from 2020/01/01, their history starts some time later?
@l-andorrà the formula is correct, otherwise there wouldn't be any prints at all
@OntradingX you cant think of any example of a loop that will not reveal your whole project?
Admin will also ask for a smaller example.
@ZakTrading the desktop version hasn't been updated in a decade, and never will be.
I use the loop block every day, no problem whatsoever. Please make some kind of example project
This is not chatGPT lol - did you try it yourself, what is your project?
@gooseman every indicator reserves some amount of your RAM memory. When you have 100 indicators with their memory allocations, there might not be space left for 101st.
Alternative structure: work with just 1 group of blocks, but run the same blocks multiple times, changing the symbol in between. You can put the symbols in an array.
You can toggle trade history by right-clicking the chart. For checking buys/sells, I would just bypass all magic/group numbers by selecting "all".


@GeoFX well, there is also many opinions on the prop firm "challenges" - are they legitimate path to career in institutional finance, or are they just get rich quick scams with extra steps.... FTMO's biggest revenue is NOT the trading profit share, its the 155€ fees from the "challenge" itself. That is their business model.
News filters dont make much sense to me, for a couple reasons:
If your constant name is "myconstant" write this in the adjust: "+myconstant pips"
int = integer, whole number
double = any number or fraction
@William-1 name can be anything, doesnt matter.
Datatype is usually double, unless you want a text setting. https://www.mql5.com/en/docs/basis/types
@unimatrix percent literally means "one hundredth", so replace % with *0.01
@forexbob-0 ok, I cant suggest anything else without seeing the project
@forexbob-0 that block can cause infinite log messages. Try replacing "close all" with the pink "for each trade" block and light pink "close" block.
Put the closing time into variable dtval, then put this condition in a custom condition block:
iBarShift(NULL, PERIOD_D1, dtval + TimeLocal()-TimeCurrent()) == 0
I dont know which mql functions automatically correct timezones and which dont, but its worth it to try a couple approaches.
https://fxdreema.com/shared/bhBUBUChb
While backtesting, close positions block will get stuck if market happens to be closed (or quotes-only mode).
It appears the block is designed to break the loop by a fatal server response, but that doesnt help in backtest.
As a workaround, using "For each position" -> "Close" loop works better.

