Posts made by miro1360

I replied you because I think where is your main issue (server scammers).

Whats your server? Is that dedicated or shared? Shared, right?
There are tricky hosting services which offers you fast xeon but in the reality they are hosting too many users on one machine via some virtualization technology - so everything is slow even if you think that you got fast server
They are using other tricky techniques. They offers for you a fast server for a low price. Everything goes so far good, until they decide to decrease the power of your hosted server
What happens after that? Your metatrader is than slower, using too much CPU. If you decide to run even more metatraders with EAs, the CPU time will be exceeded by your activity and after some time they contact you back with the message: "Hey, your CPU time was exceeded and the CPU power of your server will be limited. Therefore consider buying the "PLUS SuperFast Overpriced" plan where you get more power for your apps." - They will limit you even more, into an almost unusable state, to put a pressure on you for buying faster plan and pay them more money
Of course, if you contact them, they will beat you with standard deceptive phrases.

https://docs.mql4.com/constants/environment_state/marketinfoconstants
create new variable lot_step, and use this custom code function:
lot_step = MarketInfo(Symbol(), MODE_LOTSTEP);

there are other lot values which can be achieved:
lot_min = MarketInfo(Symbol(), MODE_MINLOT);
lot_max = MarketInfo(Symbol(), MODE_MAXLOT);

you can get them all and create some custom math for your purposes

because you messed up it completely ... I told many times, and I repeat myself once again and again: zigzag is not simple for beginners (or not coders)
... and I'm banging my head on the table, why the hell I got this idea to create the zigzag thread, because instead of explaining how the zigzag works I do the whole project for people from scratch ...

https://fxdreema.com/shared/8Xeio059c

Anyway, this is my last reply for this ZigZag thread. Everything was covered here into details with many examples ... If you does not understand zigzag, read it once again, and once again. Notice also how important are block IDs - order. If you failed, give a break for zigzag and do anything other. Come back after a few days and read everything again and give a new try.

because some TMA indicators are complicated and are not created for the signal purposes ..

for 0.1 format, do this:
TP1 = NormalizeDouble(TP1, 1);

try the code like:
TP1 = NormalizeDouble(TP1, 2);

instead of TMA use the integrated MACD with weighted price:

H1 and L1 are not future points, they are past points ... candles are marked 0,1,2,... from left (0 is the most recent candle) to the right (past candles)

the whole project is about this what you asked ...
variables:
var_zz_H0_ID, var_zz_H1_ID, var_zz_H2_ID
var_zz_L0_ID, var_zz_L1_ID, var_zz_L2_ID

if you compare them as this:
var_zz_L0_ID < var_zz_H0_ID, if the condition is true, then you know that L0 is the last zigzag leg (pointing down), and you know where is L1
if the condition is false, then you know that H0 is the last zigzag leg (pointing up), and you know where is H1

ID is not the price, it is ID of specific zigzag candle ...
prices are variables without ID (var_zz_L0, var_zz_H0, ...)

as I told you, is not that simple ... something like this:
https://fxdreema.com/shared/GmgFkC3sd
(RSI must be imported in My Indicators)

it can be simplified into Custom Code block, this is only demonstration how it can be done from blocks

... note, that parabolic sar is repainted indicator, the previous spot is sometimes repainted - some inaccuracy can appears ...

maybe between blocks is some logical mistake, I have not tested it deeply

you can do that with a few variables, it won't be so easy as one block ... at least a few blocks ...

meantime some functions were added, you can do it easily ... import RSI into My Indicators and set the Modify Variables block as this:

(I have not tested) ....

0_1556803966818_trend-direction-amp-force-index-smoothed-4.mq4

I had not installed MT4 so I edited the code in text editor without compiling test I changed tf_cu to PERIOD_CURRENT, now it should compile right

enum in meta code are just INT values, you can read everything here:
https://docs.mql4.com/basis/types/integer/enumeration

0_1556736060684_trend-direction-amp-force-index-smoothed-4.mq4

perhaps bug in fxdreema, for now try the version above, the timeframe enter in numerical format (0 is current TF, 1 is M1, 60 is H1, and so on) ...

this should open trades:
https://fxdreema.com/shared/Rd6D3Txpb

share your EA ... if it happens occasionally, it may be related to incomplete history

the error is related to the function CopyTime() ... this function is used in the block Once per bar ...

you can avoid the error using very simple alternative to the Once per bar block with custom code: (I tested it now on ducascopy data downloaded with tickstory and it worked for me)

yes but it is not that simple, you must learn how to use data from zigzag indicator (you can do it inside EA using my topics about zigzag), and you must calculate the rest of math based on that ... get ready for a hard fight
... or check web for pattern indicators ... I think someone called "poruchik" shared a lot of pattern indicators including this one for which are you asking for ... (keywords: zigzag harmonic pattern zup poruchik mt4)
... from the code of this indicator you can learn math or some conditions and apply them into your work, or you can try use whole indicators - I think they plot some text objects, you try to catch them ..

yes, that is and never will be better
google for tickstory (ducascopy), they offers good data, browse their webpages for guidance how to apply their data