Posts made by miro1360

now you should run these EAs with different settings on demo forward you can run also with small account live ... and tell us what happens ...

what happens if you run that EA from 2015?
martingale is good when it has the limit, lets say after 3 multiplies it will reset ... if no and rather continuation is taken, one must count with bankruptcy

you can recreate it, but you must have (or manually create) these indicators:
CoronaCyclePeriod
CoronaDFT_v1
Homodyne
Goertzel_Cycle_v1
Instant Trendline Filter

But I deeply doubt about profitability of that strategy

is not something in forum? I think in past it was discussed ... but I am not sure if for MT5

they used custom indicators named:
CoronaCyclePeriod
CoronaDFT_v1
Homodyne
Goertzel_Cycle_v1
Instant Trendline Filter
Moving Average (weighted mode, period 4)
another MA with dynamic period
bolliger bands
RSI
MACD
CCI
Stochastic

each indicator has own parameters,
so much combinations can contains at least the one combination of parameters, where on the specific timeframe for specific pair exist one specific profitable strategy - but that is the history where each one is general, it is gone ....

https://www.forexfactory.com/showthread.php?t=532236

The block Indicator appear is not the right block for working with zigzag.

The block "Indicator is visible" could be theoretically used, but it will not work right.
It will not work because H0 or L0 is always present on the chart (and in this block it is not related to the Candle ID) and because of that the condition "Indicator is visible" will be always true. It can be used only for the current leg, which is related to the candle ID in the block.

Few notes, because zigzag is a bit complicated:

• current leg (0) differs from other legs (1,2, - these are static), because this current leg can be repainted (and often is repainted/updated)

• zigzag leg ID is not the same as zigzag on the candle ID, but they are related (zigzag leg ID have its own candle ID and this is changed/moved with each new candle .... moreover the change of zigzag leg IDs changes whole relation)

• for identifying the presence of zigzag leg on the specific candle you must use custom code, whereby you check if zigzag leg is present on the past candles (and save such presence - save candle ID on which the zigzag leg is present)
  (I am doing this in my tutorial, where am I looking if the most present zigzag leg is high - H0 or zigzag leg low - L0)

I am not sure, if I remember these things about zigzag right, because it was long ago when I was working with zigzag, and it needed a lot of debugging, because not everything worked as expected

it is ... but wait for next value (the first logically can not be read if is not located on candle ID 0 imediatelly after EA is placed on the chart)

and change the connection between 109 and 114

this zigzag value is being checked on the candle 0 ... it has value until it is on that candle, but when zigzag is not on first candle, the value is lost ... you can prevent this loss by using temp value:

this is using two variables .....

as the alternative with one variable you can use condition check directly and than write zigzag value to the variable - but this calls zigzag two times and is bit slower as the first variant with two variables

maybe problem with Bars function ... here:
0_1540377874003_miro1360_test_1.0.mq5

@polper
no, just another overcomplication for such simple situation
use my custom indicator for it from previous post

yes, custom indicator is the best for this ...

here I created simple indicator for it:
0_1540323305338_miro1360_test_1.0.mq4
import it to fxdreema and use it as other indicators with buffers

I did one of the easiest custom indicator templates which can be understand and used ...

here is the whole code needed for this volume moving average ... the rest of the code in that indicator "template" is untouched

yes it needs a bit of coding experience, but not much, it depends ...

fast ctrl+c ctrl+v and result can be on the screen

try something from this:
https://www.forexfactory.com/showthread.php?t=354686
idea with dropbox ...

or this:
https://www.mql5.com/en/forum/180941

maybe this Candle ID in Write to file block should be 1?

try to follow this reply:
https://fxdreema.com/forum/topic/3375/Vectors-matrices-arrays-in-memory/3

at the bottom is "Create Custom Blocks", click on that and it will navigate you to this page
https://fxdreema.com/studio/MQL4

if the block order priority is important, I recommend using only numbers in the ID field

it depends on a calculation complexity, this is particularly relevant to huge arrays
in most user cases you can use double for all numbers, everywhere (including switches)