Posts made by roar

@Stevemill is it on your objects list?

@Stevemill yes

This might help https://www.mql5.com/en/articles/3331

• You need to draw your button just once, not on every tick or every chart event. Move the draw button to On Init.

• When checking the mouse clicking, you are looking for a different name - "Button1" vs "button 1"

You are talking about trailing SL, right?

To not close in loss, set some trailing start parameter, so it doesnt activate immediately.

Sure, just link your project here

Ok, maybe they just want to get people on mt5...

Heres a broker version that is at least up to date. You can use this on any broker, just change the account.
https://titanfx.com/trading-platforms/download-centre#mt4

Did you use this link in the official site? Note that you need to scroll down, mt5 is first on the page.

Anyway, you can use any broker with any mt4 program, just click File -> Open an account, and search your broker there.

@tec-nacks I cant draw any conclusions, I can only say the history data check fails for some reason.

@tec-nacks getting more data helps, thats for sure

Record the datetime value of hourly candle:

datetime timevar = iTime(NULL, PERIOD_H1, 123);

Get the candle ID from that time, in selected timeframe:

int idvar = iBarShift(NULL, PERIOD_M1, timevar);

https://www.mql5.com/en/docs/series/itime
https://www.mql5.com/en/docs/series/ibarshift

@tec-nacks the EA tries to copy some time data to array time, but this copying fails because of some data issue - do you have enough history data for all your symbols?

@tec-nacks open the code file, go to line 4857, see what array it is, see what index the EA is trying to access

If ZigZag indicator had a low at candle ID 1, the low would be printed to the candle low 1.
Candle close 1 is never below candle low 1, and close 1 never crosses below candle low 1.

Server clogging up every day, I'm starting to miss the local version...

@QuantEngineer same bug reported here: https://fxdreema.com/forum/topic/16494/close-positions-when-market-is-closed

Another workaround: close with the purple positions loop instead of blue close block.

@tec-nacks impossible with fxdreema and any other mql5 environment.

Well, theoretically you could try to re-scale one of those indicators, by checking the highest and lowest point of each indicator for the currently visible part of the history, but it gets real complex real fast

@tec-nacks that will not work. If you force Ichimoku and RSI on the same window, you will graphically see them overlap, but in the background they use completely different scales.

Mql5 doesnt have any methods for working with graphics (pixels) rather than indicator buffers and real values.

Theres a couple different methods, either way you need to learn variables first:
https://fxdreema.com/tutorial/builder/constants-and-variables

@l-andorrà computers are actually pretty bad at making "random" decisions, so they need a little help.

MathSrand() is a function that sets the starting point for random numbers generation. It takes a seed number as argument. I made a seed number by taking the tick count of current chart, and making some maths with it: take the modulo 13, multiply by 123456.

Once the random number generator has initialized, we can ask for random numbers by running MathRand().
It returns a number between 1 and 32767, so dividing the random number by 32767 will result in a random fraction between 0-1. Now we can multiply 60 minutes by that random fraction to get random minute.