fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search

    when creating candle crosses above candle high, the body is used as high not the wick? is this to fix somehow?

    Bug Reports
    2
    6
    1221
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • serioza
      serioza last edited by

      I have a pretty interesting setup but the condition written in the title needs to work but its not doing what I want.
      The body of the candle is being used as high and low not the top or the bottom of the wick
      How is this to correct?

      1 Reply Last reply Reply Quote 0
      • roar
        roar last edited by

        By default, high and low are the upper/lower wicks of the candle.
        If you need the body values, use candle open and close.

        Need small help? Tag me in your post
        Need big help? https://www.fiverr.com/big_algo/automate-your-winning-strategy-in-mql4-or-mql5

        1 Reply Last reply Reply Quote 0
        • serioza
          serioza last edited by

          unfortunatly thats not the case it doesnt work like that instead the body is the trigger see attached setup0_1574271025179_candle condition.mq4
          use on any timeframe

          roar 2 Replies Last reply Reply Quote 0
          • roar
            roar @serioza last edited by

            @serioza But your project draws arrows on candle close, not high/low ?
            0_1574272317527_eff86c78-ef3f-406a-a5e6-a24635d593ea-image.png

            Need small help? Tag me in your post
            Need big help? https://www.fiverr.com/big_algo/automate-your-winning-strategy-in-mql4-or-mql5

            1 Reply Last reply Reply Quote 0
            • roar
              roar @serioza last edited by roar

              @serioza Ah, I think I got it now. The crossing condition doesn't work tick-by-tick, but only bar-by-bar.
              So you can't use that condition to track intra-bar changes.
              To track intra-bar changes, you could use a variable to store the last tick values.. This setup finds the crosses you need:
              https://fxdreema.com/shared/ILF2RuVjd
              0_1574274845466_df8001c9-b00f-46de-890d-ef796591348a-image.png

              Need small help? Tag me in your post
              Need big help? https://www.fiverr.com/big_algo/automate-your-winning-strategy-in-mql4-or-mql5

              1 Reply Last reply Reply Quote 0
              • serioza
                serioza last edited by

                wow thanx alot man this is exactly what I need!

                1 Reply Last reply Reply Quote 1
                • 1 / 1
                • First post
                  Last post

                Online Users

                M
                R
                G
                T
                G
                Y
                C
                S
                S
                S
                A

                22
                Online

                146.7k
                Users

                22.4k
                Topics

                122.6k
                Posts

                Powered by NodeBB Forums | Contributors