Posts made by miro1360

you can not convert mq4 to mq5 for renko chart generators,
mt5 renko is very different from mt4, you will be unable to convert it, don't waste your time with that
moreover, renko is not as good as it looks, it filters out time, but that's about it, time is important so you lose a lot of information
those offline charts for MT4 are generated from an incomplete tick history, or if they are generated forward, they will look different on each broker (due to different injection of tick data at highly volatility events) ... and you can easily lose them, they can be rewritten by the generator from a "simplified" history of 1-minute candles

only this for current chart:

or modified code for all charts with a specified pair: (untested)

right, both answers are correct, this type of indicators is used only for visual analyzing the history, not for trading, not applicable for EA

trust me, it can be done with a bit effort ... I shared everything to complete it for MT5, simple by "copy and paste" particular blocks perhaps the hardest part is to understand logic behind this zigzag to work with it properly ...
https://fxdreema.com/shared/NSdwI6DFc

do it better outside the converter ... block by block manually

I'm afraid it won't be possible to do exactly what you want. Ideally if you fit every EA for desired indicator.

Function for custom indicator used in the code is this:
https://docs.mql4.com/indicators/icustom
there is not much to be done there (due to the possibility of different types of input variables)

partial solution could be, left the Param. field empty and change the input parameters manually in an indicator code, but it's quite uncomfortable

is mode buffer right in the second example?

problem is, these arrows are not in buffers (they are just objects) ...
you can check with an EA condition if a new object appears on the previous candle (work with objects, not buffers) ...
...
or carefuly check how or when the arrow appears ... it is when all buffers are aligned as green or red - use condition and check all buffers

if I remember right, it is expected. The border color has to be specified for Edit field and Button object. If it is not specified, then the color of text is used for border (this is how mql code works). So as you found out, use the same color for bg and border. If you use multiple edit fields next to each other, leave a free pixel between them and the result looks as border-less.

just a fast fix
DisplayType value is now disabled (it should print all on the chart)

0_1589950552038_t3-high-low-activator-mtf_fxdreema.mq4

moreover, fractal repaints sometimes you have to catch the signal on the third candle
Pipholic SR indicator is based on it

if it is once good and once bad, then maybe there is a problem in the missing historical data, or excel reformatted csv while opening it (check csv in another editor)

it is working fine but you don't know how to use it I'm not sure if you learn it, not everything is easy for everyone ...

and yes, it slightly repaints
https://fxdreema.com/shared/nFdV3NTVc

so you have to work on the right logic try add another variable (after the Change Timer period block) ... draw it in another diagram (the way you understand) if you have trouble understanding collisions in written logic

I am not sure ... perhaps do this? idk why ...

do you mean this response? if so, you can try it and tell us if that worked

Waiting for the response is executed by a WebRequest() function which is part of the block "Send HTTP request" and sadly it is synchronous - it breaks the EA and waits for the response from the requested server in a specific delay (can be set). If the delay elapses without the response, EA continues in a normal cycle. If this whole thing works I can't confirm because I've never tried it If you want something more dynamic, you can try at least 2 possibilities:

• program your own waiting server outside MT4 (use something as simple as the python again)
• lazier (and still functional) workaround: create another EA - purely only as a waiting EA for the request and bridge it with your main EA using global variables (global variables in MQL == Terminal variable in fxdreema) ... if you need more "asynchronous" requests, simply open more waiting EAs and more variables

by automated naming for variables
on the other hand, if EA is sold as profitable but ruins the customer's accounts, who is the thief