I guess this problem was universal. I checked www.fxdreema.com on the site http://downanalyze.com/check/fxdreema.com and it confirmed that the entire site was down for about 18 hours for everyone around the globe. The good news: It's up again.

@fxDreema Confirm that the importation is a real issue. Also, when I attempted to delete projects by clicking the X at the "Load Project" window, the software asked for confirmation and removed the selected project after confirmation, but when I reopen the "Load Project" window, the deleted projects are still available... Last, the Trace block doesn't trace the same indicator it traced before the blackout. I still investigating it on my side but so far it seem that the problem resides on FxDreema server, since I can trace this indicator with the desktop version of FxDreema (with some limitation since this version is not fully complaint with new updates of the online software) . It seems there are serious issues with the working copy of FxDreema after the blackout. Please check it. Thanks in advance.

I guess this problem was universal. I checked www.fxdreema.com on the site http://downanalyze.com/check/fxdreema.com and it confirmed that the entire site was down for about 18 hours for everyone around the globe. The good news: It's up again.

Bossx, Sorry for being so late (2 months late) to reply. I don't understand your question. The indicator is attached above and the code is unavailable since it is an ex4 file. This topic deals with setting up correctly the enum type of parameters in indicators for which the code is unknown.

Thank you Miro!

I actually was able to solve it myself, as I explained here: https://fxdreema.com/forum/topic/4842/lack-of-support-to-enum-datatype/4. It is pretty much like your solutions. I placed my enum list in the Global Variables section of the FxDreema EA (see picture in the link). I also changed the input parameter at all the iCustom functions as seen in the picture. I wish FxDreema would be able to do all this work for us.

Well after playing around I found how to use enumeration in FxDreema EA. Inserting the list here in the following format does the trick:

Then you have to manually change the enum value at all the icustom lines, as follows:

And then it compiles with no issues

So if I import the indicator exactly as it appears in the Input parameters, as follows

The default value is not liked by the EA, as seen here

And confirmed by the compilation results

Is there any other way to import successfully an enumaration value?

And to be more specific:

These are the input parameters of the custom indicator "ocn_nma_3_1.ex4"

"Price to use" is enumaration data type

I used "enum" as data type

The enum list was casted here in the EA

This is how the enum appeared in the iCustom

And these are the results of the compilation

Can this be resolved? The indicator is attached as it's available on public domain (coded by Mladen - thanks!)

0_1499663853086_ocn_nma_3_1.ex4

FxDreema doesn't support enum datatypes. Some great coders, such as Mladen, are using enum frequently for Price type. Even when I imported one of his "mq4" indicators that has enum Price type I could not use it as costume indicator in FxDreema because of this datatype. Importation of one of his "ex4" indicator ended up the same. When I tried to use "int" with the default value of the enum (which was "close"), I got errors message on this "close" during compilation.

Are there any new ideas how to tackle this deficiency?

Thanks Ron

Hi Miro,

FxDreema doesn't support enum datatypes. Some great coders, such as Mladen, are using enum frequently for Price type. Even when I imported one of his "mq4" indicators that has enum Price type I could not use it as costume indicator in FxDreema because of this datatype.. Importation of one of his "ex4" indicator ended up the same. When I tried to use "int" with the default value of the enum (which was "close"), I got errors message on this "close" during compilation.

Awhile ago you suggested to try a work-around it, but I can't find my post in the forum where you suggested it. Do you have any practical experience with converting enum datatypes to a list of the usual datatypes, and if yes could you please share with me one or two segments of codes to teach me how to do it?

With your permission I'll also post this question as a new topic in the forum to check if the moderator has any new ideas.

Thanks Ron

Thank you very much Miro! I figured out there should be some easy way to do it with which I was still unfamiliar.

I'm almost convinced someone had asked this question before me but as much as I can tell searching with Keywords or short phrases is unavailable on this forum. I wish this would be added so that we would not repeat asking the same question again and again and again....