Again, the Trace block is only for testing purposes, it's not designed to be used to indicate something. Trace is NOT an indicator. Trace shows you the history of a value, including values such as EMPTY_VALUE or -EMPTY_VALUE.
These lines are oscillating because the values you prot are oscillating. These lines are Ask and Bid prices shifted above and below. These are not Highest or Lowest prices of something, which is the case in Donchain Channel.
Ok, I need glasses 8-)
Anyway. It's had for me to say what is wrong. It appears to be working for me - http://prntscr.com/alpk13 I don't know... look for errors in the log?
I think that it works now. But in case of bugs like this, there is a special subforum - viewforum.php?f=3
Whatever the problem is, I have to see it in order to fix it. Give me something that I can try 
I tried something, but it works for me - https://fxdreema.com/shared/5ygU2qHWd
When you backtest the time comes from the candles, I don't think you have control to change this. Whell, you have... if you use external history data.
By the way this also compiles without problems:
iCustom(
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4
);
Nothing is wrong with the buffers. It appears that iCustom always gives error when the parameters of the indicator are 60 or more. It works with 59 or less, but once you reach 60 parameters it starts to fail. Or in other words, if all parameters in iCustom are more than 64, it fails. Note that this function does not contact with the actual indicators and it does not now how many parameters it really have.
Try this:
iCustom(NULL, 0, "MyIndicatorName",
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,0,
1,2,3,4,5,6,7,8,9,
0, 0);
This compiles successfully, but put one more parameter anywahere and it fails.
What information do you have here: http://prntscr.com/aln6cn
At least on backtesting, this works for me - https://fxdreema.com/shared/QiVNz2cbc
Wow, this error shows some Assembly code! This was bug in the MQL4/MQL5 compiler. I updated it and not it should work. But because they also changed the way files are compiled (now metaeditor.exe is used instead of a standalone mql.exe file), I expect other problems when compiling files
Even if you choose Money, this block still calculates the Average value, not the sum of all profits. For the sum there is another block - Check current unrealized profit.
Also, there is another way - https://fxdreema.com/examples/#Bucket-of...
Only for My Indicators (in Condition) there are extra options to get various values - http://prntscr.com/aktb2i
http://i.imgur.com/Ei8KQel.png
... if this helps.
You can also store value in some variable and then use it later. Or put object on the chart and then get it's Time or Price. It depends.
I personally don't want to do that, because pending orders are much more unpredictable and I don't even know how these MM options should work
Try this - https://fxdreema.com/shared/FbPnl5L7
This creates Buy trade with SL = Lowest price of the last 10 candles and TP is calculates as the same distance. I want to get the difference between Bid and the Lowest price, but because I selected the Lowest price and I want to include the Bid price in the Adjust field, I use this formula to invert the calculation: *-1)+Bid
Bid is predefined variable in MQL4. MetaTrader puts the value of Bid on every tick. By the way there is no such variable for MQL4. Why Bid... because candles are built out of Bid prices.
But note that this project is dangerous! Put it to test and you will see why. Before going to Buy, the difference between Bid and the Lowest value must be checked.
You can also use Variables and calculate these values in a different way I just wanted to show you this example that uses no extra blocks for calculations.
Can you send me some .mq4 file? The last time when I tried this, it worked, but I'm testing it with 3-4 blocks... who knows what is wrong with this project...
https://fxdreema.com/shared/hsDOwmgNc
http://prntscr.com/akfomc
http://i.imgur.com/IdrHrCB.png
If the ID is 0, both are the same. On the picture the ID is 1. And it looks that High (H) is the previous high that is found, while Higher High (HH) appears to be the previous High that is above the current value.
This is moments later - you can see that when the current value reached the yellow line (HH1), a new HH is found that is higher than the current value
http://prntscr.com/akfpyt
http://i.imgur.com/Yfuvwdw.png
Once per bar. Take a look at the second example here. And at the first as well - https://fxdreema.com/examples/#Simple-Programs
It worked only with whole numbers. I changed that and now it works with values like 0.5. But also note that there is something called Lot Step, which is the minimum lot step and comes from the broker. If this value is 0.1, then you can open lots like 0.1, 0.2, 0.3, but notthing in between.