fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    1. Home
    2. re0306
    3. Topics
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 31
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by re0306

    • R

      understand slippage
      Questions & Answers • • re0306

      2
      0
      Votes
      2
      Posts
      381
      Views

      fxDreema

      For modern brokers this parameter does not work anyway. Search something like "ecn slippage" and you will probably understand why. To be honest, I don't fully understand it, I only know that the slippage parameter is most probably useless 🙂

    • R

      "Trailing Stop pending order" in two direction
      Questions & Answers • • re0306

      8
      0
      Votes
      8
      Posts
      1290
      Views

      fxDreema

      "check age" works with OrderOpenTime(). There are only few available functions to get parameters of the orders - https://docs.mql4.com/trading OrderOpenTime() and OrderCloseTime() are two of the parameters, but there is nothing about the last modified time. In theory such time can be collected while the EA is working, but I prefer to work only with functions that would continue to work the same after the EA is restarted.

      But I don't see why you need Modified time. Isn't your idea to move orders every X seconds? "Once per seconds"... I will suggest to put this block on top level. I don't exactly remember how this block worked, but I think that it doesn't work at exactly equal periods of time. If you want exactly 5 seconds, then you can work under "on Timer", but in this case you will not be able to backtest this functionality because "on Timer" doesn't work in the Tester.

    • R

      Check last position...
      Questions & Answers • • re0306

      11
      0
      Votes
      11
      Posts
      1800
      Views

      fxDreema

      In Example 2 those "Bucket of.." blocks are working pretty much like "Pass". What these blocks do is to take a look at the existing trades and prepare some array that can be used later. There is no visible result from them, but if you run them, they can pass. And this is what happens - they run on every tick and because trades exists, they pass. Why they run on every tick... because why not, these are the rules for blocks who are on top level 🙂 When they pass... you make even more trades 🙂

    • R

      Bug in TRAILING STOP in MQL5 Version
      Bug Reports • • re0306

      20
      0
      Votes
      20
      Posts
      6226
      Views

      S

      __This is what I tried:
      http://prntscr.com/bmqdi4
      And this is how it worked:
      http://prntscr.com/bmqdbh

      I got some modifications. I don't know what does not work. I need more information, what I am missing here?

      shafqat, I never tried the built-in trailing stop, but the block should work. There are so many settings, because people wanted them.[/quote:3pfe8g0u]
      thank sir you resolve my problem......now point clear..Thanks alot

    • R

      I do not understand a parameter inside TRAILING STOP
      Questions & Answers • • re0306

      10
      0
      Votes
      10
      Posts
      1063
      Views

      R

      .

    • 1 / 1