Importing MT5 example indicator RSI.mq5 is failing
-
I cannot find a workaround for the following issue. Please help.
When importing the example RSI.mq5 indicator (unmodified, out-of-the-box MT5 install), the default parameter is not recognized. Screenshot:

After replacing the default value for InpPeriodRSI with "14", the import works.
EDIT: Meanwhile, I replaced data type "variable" with "int". With this, an EA using Examples/RSI.mq5 can be compiled. A similar issue persists, however, with another imported custom indicator. Even after replacing the incorrectly offered string value with "14", the parameter is missing in the generated source-code. When I manually insert the missing parameter in the handle-generating code, everything is working. Seems to be a bug in the handling of custom indicator imports.
Using this custom indicator in a condition block seems to work flawlessly.
The EA, however, does not compile anymore. Screenshot:

Compiling the EA in MT5:

What could be the problem?
Download link for the imported indicator:
RSI.mq5 -
@sparrow I'm not a programmer so I can't provide a solution for that but you can try to emulate the parameter as explained in the second half of this nice tutorial:
https://fxdreema.com/forum/topic/4208/tutorial-06-my-indicators-in-fxdreema
-
Also realized that data type "variable" was inserted and corrected this. Still had problems.
Seems like the message string, i.e. the PrintFormat() argument, confuses the parser.
Weird that importing a standard MT5 example custom indicator is so hard.
Anyway, I got used to that but figure that many noobs - like I was - struggle with that. Might not be so good for the reputation of fxDreema. The graphical coding UI for MT5 that I love.
-
@Sparrow
After a manual update of a custom indicator, it seems that the fxdreem output of mt4/mt5 may not update until some hours later. More likely to happen when items are corrected rather than appended. -
Well, the parameters extraction happens on the browser and the code I wrote for this is not very capable, it doesn't really understand the MQL language. In this case I can see why the problem happens:

the code that I wrote thinks that the variable is defined on line 36 where this is clearly a string. In reality the variable is defined at line 20.
The correct values are:
data type => int
name => InpPeriodRSI
default value => 14