Your parameters are 21,3,0
But again, better add this indicator in the database from My Indicators, it's up there in the main menu. I already gave links that explain this + there is also inline information there in this option. Your indicator is pretty simple, only 3 int parameters and 2 buffers
Well, I don't have this indicator, so I don't have an idea even how it looks like. Look at your logs to see if everything looks fine there.
I don't get the idea of this: http://prntscr.com/6x8hkh
Two operands compared with ==, both are exactly the same. This condition will always be true, the same as if you don't have this block at all.
Here is more about indicators: https://fxdreema.com/documentation/you% ... indicators
It was also hard for me to read it sometimes. I changed it to almost white
The whole idea of "My Indicators" in fxDreema is to have database of some indicators and use them easily in blocks like Condition. This database does not contain the actual indicators, only their file name, input parameters and buffers. This is all that is needed to be used in the output code. A function called iCustom() is used and it needs only the name of the indicator, input values (not even parameter names, it needs their values only) and the buffer number to use - 0, 1, 2, whatever.
Yes, you can always add indicator in fxDreema. You can't use the .ex4 file, but you can add it's information manually. All that is needed can be found in MetaTrader, as in the pictures on the bottom here: https://fxdreema.com/documentation/work ... indicators
It's not the location, it's my decision. When the EA is generated it first excludes all blocks that are left alone. Again, because my initial idea was to be able to keep some blocks around like this for "later use".
Now I don't like this concept very much, because when I left few blocks like this, I just forget what was their idea. So I am thinking to make those blocks to run and keep blocks for "later use" somewhere else, in some isolated field... if anyone needs that at all.
Also, I am thinking to remove block numbers. Now what matters (when connected in parallel) is the number of the block - the one with lower number will run first. But what if the block on left (or top) runs first? This is something that I didn't tried yet, but I will eventually do.
The Timer starts with the EA normally. This is a clock and does something on a regular basis. Then it runs once on every X seconds. But it does not care about the ticks. You can have 0 ticks in 10 minutes, but the Timer will run on every X seconds.
I'm suggesting this event because you want specific time that does not depend on ticks. But I don't think that you really need it, I think that the time period can work well. Something like Time filter -> Once per bar, or the opposite.
In the output MQL4/MQL5 code all blocks are functions, all connections are function calls. At the end of each function there are function calls to the next functions (blocks) connected after the current one. What happens when you run a function which at it's end runs another function Chain reaction. It goes this way until there is no function to call.
Some people think that if a block can't pass, the EA will sit there and wait while it passes. But it does not work this way.
What does not work now? Because all "Print message" blocks now are disabled and they basically don't work 
So even if conditions does work, no print messages can be seen.
Here is some example: https://fxdreema.com/shared/p4ttu6tud
Here I used Martingale, which normally doubles the lot size on loss, but I customized it to half the lot size on profit. Then I separated trades in two groups - 1 and 2, because Martingale normally don't care what type was the last trade - buy or sell - but cares about the group.
There are probably other ways to do this, but I choosed this one, I think this uses less blocks as possible
You can try this under "on Timer". But note that this event can't be backtested, because the Tester runs the EA by ticks
The first link above
Also here: http://docs.mql4.com/globals
All input parameters must be there. If you have 1 parameter, fine, but if you have more - you must write all of their values.
But I will suggest to put the indicator manually into the system: https://fxdreema.com/documentation/work ... indicators
There are multiple pairs of Labels and Values. Label = the name of the thing, the title which does not change. Value = it's value.
In your case:
Label => MACD Val1
Value => MACD_Val1
Just try it!
Recently I added brand new block for comments and I renamed the old one to Comment (ugly).
I got this question multiple times, but unfortunately there is no easy way to do it in fxDreema. The main problem is in the interface of Condition block. It has 2 sides, left and right, but you can select 1 indicator for one of them. So I don't have the idea how to make such an option in the generator. Otherwise I know that this can be done with this function called iMAOnArray()
That is true, the returned values are for horizontal-looking fibonacci. Unfortunately there is no native function to get these values and I'm using custom made calculations. I don't know ho to do these calculations for all the other fibos
This link sends everyone to it's own projects Only I can see your project, which is chinese, I believe. I don't even know it indicators with such letter work. You can check them with "Indicator tester" to see if they work.
The idea is simple, but because it's also custom, it requires some more checks:
https://fxdreema.com/shared/oLBgLGedc