Posts made by fxDreema

You tried it?

Indicators does not exists in EAs or Scripts, they are something separate

Just create some trade from another "Buy now" or "Sell now" with the initial lot when you want to reset Martingale

Here is more about this crossover - https://fxdreema.com/demo/mt4-crossover-indicators
But you have two values and they don't have previous state

Stop or Limit - this depends on where the open price it. This is how I did it initially and this is how I still understand it better. I never understood those limit and stop things

By default you get Buy order that is 20 pips above the price ot Sell order that is 20 pips below. This is because "Price offset" is 20 by default. But this value can be also negative. Try -20 and the order will go on the opposite side of the price.

For some reason I don't understand what is the issue here 1 short, 2 shor, here and there... I'm confused

If I try this, no MA lines appear on the chart. Only after the backtest. But while testing there are no indicators on the chart at all - https://fxdreema.com/shared/O73N0QUud

You have two options for Reset. "Reset after how many losses?" and "Reset after how many profits" These are normally fixed numbers, they don't change. But if their value comes from a Variable, you can control them from outside the block by controlling the variable.

Or just create trade with your initial profit at any given time from another Buy now/Sell now (where Maraingale is not present).

It's so easy to get the current Account Balance, Account Equity, Account Profit or the total profit realized by group of closed trades. Or the total unrealized profit (by currently working trades). It's just a bit harder to get the profit of closed + working trades, bit it's not impossible. I just don't understand which of these variants do you want to use.

Turning blocks on or off is pretty obvious. It's just action that can be done. What I don't understant is the profit calculation.... or whatever it is. Because I posted some example above of how to get shanpshot of Equity and then use it later.

I told you few times. "OR" is like Once per tick. You can run it 100000 times in that tick and it will pass 1 time. On the next tick - the same happens. "OR" block is not aware of other blocks. "OR" does not care what is above or below it. "OR" does not have control over other blocks.

With "OR"
https://fxdreema.com/shared/bXPswk7xe
http://prntscr.com/aafjco

No "OR"
https://fxdreema.com/shared/JNLyZbopc
http://prntscr.com/aafjqf

http://prntscr.com/aaffs7
Try to set this string value as 00:00

http://prntscr.com/aafc35
This thing appears to be 0. I can admit that I have no idea what this value is. It comes from here - https://www.mql5.com/en/docs/constants/ ... oconstants - search for SYMBOL_LAST. It is described as "Price of the last deal" and back in the day I added it in "Condition" just because it exists in the documentation, but what it does... I don't really know.

Then I don't understand what you want. The opposite of trailing stop for me is... trailing profit - the idea to trail Take-Profit, because normally we work with Stop-Loss. I don't have an idea what Trailing Start block should be

This shows the sum of lots for buys, sells and both https://fxdreema.com/shared/xN2HKsDyd

There are blocks "Buy pending order" and "Sell pending order". Also there is "No pending order" block, as well as "Check pending orders count"

Becaused of this - https://fxdreema.com/demo/mt4-wrong-closing-rule
"OR" is not needed.

The very first example here - https://fxdreema.com/examples/ Use "No Trade"

Oh no, Terminal Variables used again... now I will definately rename those.
Do it like this here - http://prntscr.com/a95vic

I don't even know what FORTS is

Well, blocks 701, 1183 and 1288 will all run once 9927 passes. That "OR" below cannot stop this. Obviously in this situation the behaviour of the yellow output in case of crossover does not help. But this rule for the yellow output for crossover is as old as fxDreema, this was one of the first features. If I have to decide now, I will probably choose to not do it like this.

Fun fact - in the beginning Condition and Formula blocks were 1 single block

This video is not for people with photosensitive epilepsy

CHART_WIDTH_IN_BARS and CHART_WIDTH_IN_PIXELS are read only. CHART_HEIGHT_IN_PIXELS is not, but It appears to be woking only on indicator subwindows.
Open new chart, add some oscillator and play with this EA:

int subWindow = 1; // 0 is the main window, 1 is the first subwindow and so on...
int setpx = 20; // initial height

void OnInit() {
   ChartSetInteger(0, CHART_HEIGHT_IN_PIXELS, subWindow, setpx);
   EventSetMillisecondTimer(5);
}

void OnTimer() {

   if (setpx > 300) {EventKillTimer(); return;}
   
   ChartSetInteger(0, CHART_HEIGHT_IN_PIXELS, subWindow, setpx);
   
   Comment(
      "Main Chart Height: " + ChartGetInteger(0, CHART_HEIGHT_IN_PIXELS, 0) + " px\n" +
      "Subwindow Height: " + ChartGetInteger(0, CHART_HEIGHT_IN_PIXELS, subWindow) + " px"
   );
   
   setpx++;
}

If you set subWindow to 0, nothing happens.