____On the right use Value -> Numeric if you want the number to be fixed. You can use it as a Constant, also in the same place (right-click over the input field) - for this you just need to define a constant. Or you can use some horizontal line.

But what is the most important here, DO NOT use == in the condition when comparing two prices. Use everything else, but not ==. If you think for a while, you will understand why.[/quote:3atvaiba]

Ok I can use > or < for the trigger but I can not figure out how to code it. How do I use horizontal line or price value for the kill all switch?[/quote:3atvaiba]

I think I have done it. You just need the place the ea according to the price. If the price is gonna hit the kill all target from above you wanna use the above ea, same for the opposite. I tested it few times I think it works. Here I post the ea in case someone needs it.

......
Kill all from above.ex4
Kill all from below.ex4

if you are trying hedging strategies, my opinion about these is that they are overcomplicated Martingale strategies. The same result, but much, much harder to make and maintain. The easiest thing to do in your case is to just close those buy trades and think fresh what to do next.

If you want to calculate the total lot size of those trades, it's a little bit complicated and it looks something like this: http://prntscr.com/85eof1
http://i.imgur.com/OtO811w.png

For the future I was planning a block that will load a group of trades and then in "Condition" and all the other blocks various parameters will be available, like Average Lots, Total Lots, Min Lots, SL, TP... stuff like that.

Sanks

I don't understand sentences without commas even in my native language. Some screenshot? Or at least tell me how things must happen in steps, like this:

Step 1 - Open Buy pending order...
Step 2 - When the price is... do this...
Step 3 - Something else...

Thanks for the ideas. I will test them.

Please don't get rid of those checkboxes. Some of us rely on them. I've tried using constants but can't get it to work for me. I'd rather spend my time building and testing EA's with functions that are currently working for me than trying to learn a bunch of new ways to work with Dreema before I can proceed. Like many features with the product, I'll probably eventually learn to use them in time, but for now the checkboxes are working just fine.

Of course there is a way and this way is much better post/9920

I just realized that someone can lose his good settings because now these optimization input parameters are not written to the output file. Somebody having this issue?

Wow, I tried to copy 1 block and all the blocks were copied. The good part is that even if there are bugs, the whole system is written in a better way and it's easier to track and fix problems 🙂

So now all the formula results will be written in Variables. If you already have "Formula" block in the project, some Variables must be automatically created, otherwise you must create them manually and give them a good name that means something.

I personally prefer the local Version way more than the webversion. It's just so much more responsive, I'd be sad 😢

FIREFOX NOT WORKING?

Тия променливи преди ги бях кръстил "Global Variables in MT4, ама хората постоянно ги бъркаха и ги прекръстих на "Terminal Variables". Сега пак ги бъркат 🙂

Тия променливи не са ония променливи, не са сините променливи. Променливите на терминала (MetaTrader) са както бисквитките при браузърите, ама за MetaTrader. Натисни F3 на MetaTrader и ще ги видиш. За съжаление те самите са си ги кръстили Global Variables.

Как да се реши проблема... Value -> Numeric, и там слагаш синята променлива.

__Never use == to compare prices! If you use it, then there is a huge difference between prices 1.23456 and 1.23457 that otherwise looks very similar. Use anything else, but not == for price and indicator values.[/quote:2uqqkwqs]

thanks for the xplanation 😁

ok. thank you. i retest it. happy week end

Can you show some project?

The timer also works only for live trading, it does not work for backtesting. Look at the very bottom here: http://docs.mql4.com/runtime/testing The timer event is working by itself and it does not care about ticks, it's like a clock.

MagicStart exists in all EAs. To use another inputs, use "Constants (Inputs)"http://prntscr.com/81ooy1

I don't understand the problem with Renko, but there are many Renko-creating-EAs-and-indicators out there, so I can't tell exactly what is wrong. But I feel that you can have less connections and work without this "AND"

I don't know really, I'm not a specialist in this field

Again, the option that you have on the screeshot above does the calculations like this:

You have 10,000, then with the setting of 10(%) the lot size will be exactly 0.01, not 0.03, not 2. 10% of 10,000 is 1000, which turned into lots equals to 0.01, at least on EURUSD and similar There is no margin stuff here. Yes, if the calculated value is too low, the lowest possible is taken, and if it's too high, the highest possible is taken.

thanks I will try it out