Posts made by fxDreema

I got some pending orders on my backtests. At some point I even have multiple orders at a time, this is because you have different group numbers for "No trade..." and for pending order blocks

Ok, try +10pips

+0.0010 will work better This field is not aware of what type of value the operand is... and now that I am saying this, maybe it's not a bad idea if it can be aware

Probably, in form of indicator

At least this was my idea. This is like a snapshot of the project, but it also works as a project.

Indicators are added once and they are not per-project, they are accessible from all projects

Oops, I forgot something, now it should be ok.

Not easily. The Comments that you can see now on the upper left corner of the chart is native from MQL4/MQL5. I will do something about this eventually, because people are asking questions like this from time to time, but now it's only the default Comment. Also, you can always create some Text objects here and there.

The code that is generated is unique and it represents the current time actually. So every time it is something different.
I have a script that deletes those project that were not visited for some time. I think it was 1 month, but I'm not sure, I have to check this.

Why do you want persistent link?

I don't think so. Formula results are simple variables, while indicators are arrays of data. This block reads some values of that array. And you want to compare two indicators, two arrays.

Nope. But it is a good idea, at least indicator parameters can be added into the project data of the EA. Well, I don't know when this will become fact

Ok, I added this option: post/8017
It was requested few days before, so I guess it will be useful

I will add some option eventually, but now you can do it like this https://fxdreema.com/shared/UGLN2l79 or if you can calculate SL before Buy now

No, I didn't fixed the indicator, for me this is just another indicator from internet that fxDreema needs to work with. But sometimes fxDreema has bugs

Now I fixed the problem with that Symbol_ parameter, it appears where it should appear. But the other thing, the first problem I mentioned, I will leave it that way, because I want datatypes to be free. Well, some datatypes obviously does not fit. In this case "int" works.

I fixed the last problem, you can re-upload the indicator and that parameter will be second, not last.

Now I get this error when I try this on a Visual backtest: CapitalManagerDR EURUSD,H1: ObjectCreate: error 4202
Well, in this case I thing the indicator is "wrong". This particular indicator creates those candles using short trendlines (and using data from the hidden buffers), but somewhere in it's code ObjectCreate() fails to do that on visual backtest. Otherwise I think this does not appear on live.

Buffers are fine.

Damn, for some reason this parameter called "Symbol_" is placed as the last parameter, it must be the second parameter. I still don't know why, but you make sure that all parameters are added properly, their order matters the most. If not, the indicator will not load or will not stay loaded correctly.

Buffers 0, 1 and 2 have no color by default, but if you add colors to them you will easily see what they represent. Actually, fxDreema reads this information very well.

But there are some problems with input parameters and you will probably get compile errors. The answer to this is here, I wrote about this recently:
topic/2795

In your case, you have two enumerations - indicators and ENUM_RANGEMODE. Make them int in the indicator definition and use default values of 0.

That's why indicators exist - they get the informations from candles, do some calculations over that information and produce other information (or signals) that you or the EA can use in order to decide when to trade. MA, RSI, BB, CCI, Stochastic... different indicators for different needs.

Candles themselves are also information, and each candle can be easily accessed from the EA. You can read O, H, L and C of any candle that you can see. Also, if you ever need this, here is a block named "Single candle template" that can match certain candle form.

Yes, this field is not only used to add a value, you can write whatever you want there and it will be put as it is in the final file. The content of this field is appended to the value of the operand, you can see how it works if you look at the code of that block.

I'm looking at your projects, but I can't find one named "BOH" or even one that has Constants defined