Topics created by ylidor

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 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....

Can you please share the link to your current project?

Under "on Tick" each block that is on top level (nothing connected in its white input) runs on every tick. When you have group of blocks and one of them can't pass, then this is the last block to work. But if you have multiple paths after one block, each path will run. Look at these examples https://fxdreema.com/examples/#Interface

MetaTrader already provides arrays with candles data and indicators data. In all moments you can get O, H, L and C of candle 17 for example. The same goes for incdicators - by prividing Candle ID, you can get the value from that candle just like that.

It's a little bit harder when you don't know the ID of the candle from which you want to get a value. But it depends, some things are already avalable, like the Highest value of N candles for example. Also, for custom indicators (My indicators) there are extra options in More settings

No problems. Instead of playing with this indicator I found that the indicator provided by miro (Fisher_org-v11.2) is useful in FxDreema and that it is actually a pretty good non-repainting replacement (for my purpose) to SolarWind (thank you so much miro!!).

This current topic is now resolved. However, since there is no formal manual to FxDreema I need to ask you a general question which deserves a new topic for everybody's education. It relates to the general approach in FxDreema to 2 conditions or more that have to be met before a market order is placed but they span over several bars. See you there.

This is how the indicator works. It's not the "Indicator tester" or "Trace" that shows wrong values. Sometimes I introduce bugs in the code, but I'm 99% sure that the block is working very fine 🙂

The huge number (21... ) is also known as EMPTY_VALUE and this number is how indicators tell the EA that there is no value to be shown. That's why the constant is called EMPTY_VALUE 🙂