fxDreema

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

    Bug in blocks

    Bug Reports
    2
    8
    3156
    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.
    • tcanuto
      tcanuto last edited by tcanuto

      Look what's happening:

      0_1487793513032_Captura de tela de 2017-02-22 15:35:04.png

      I also have 2 similar versions, but using the same parameter. But the results are different.

      I also discovered that the parameters in a block was changed alone, I do not know if it was because I imported a project already saved on my PC, I do not know why.

      shared/YNDwt25jc
      shared/ZEX1LxCnd - Add Weekday filter block

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

        This cross width thing is probably cosmetic defect, not something fatal. That input field is always there, even if it's not visible.

        I'm more afraid of that parameters change. The thing is that fxDreema become complex years ago and since then I'm only trying to make it simpler for me, to minimize potential problems when I decide to update something. But after all my efforts, bugs are still possible. Give me more details about this parameters change problem - what exactly happens and how can I cause the problem, so I can see it and fix it?

        By the way, I discovered this problem minutes ago: https://fxdreema.com/forum/topic/4449/february-2017

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

          @fxDreema said in Bug in blocks:

          This cross width thing is probably cosmetic defect, not something fatal. That input field is always there, even if it's not visible.

          Thankfully it's only an aesthetic problem.

          I'm more afraid of that parameters change. The thing is that fxDreema become complex years ago and since then I'm only trying to make it simpler for me, to minimize potential problems when I decide to update something. But after all my efforts, bugs are still possible. Give me more details about this parameters change problem - what exactly happens and how can I cause the problem, so I can see it and fix it?

          By the way, I discovered this problem minutes ago: https://fxdreema.com/forum/topic/4449/february-2017

          Yes ... I'm suspicious of this. Once I happened to change the constant inside the block.
          Already in these last days I had a problem in the block Close Positions, which I had left in the Filter by type as Buy and Sell, but it took almost a week to find out that the problem was him, since I had changed in the project for Buy only. So the results did not beat.

          Now I've reviewed all the blocks, but they still have different results for the same parameter.

          I think I have a problem with the second link project.

          Maybe when you import a project, you should also change the blocks parameters yourself.

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

            Once you're doing something, could you contact me so I can generate mql5 and ex5 from my projects?
            Well with that I will do new tests, and if the result hits with the current version that is correct, I give you feedback.

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

              I discovered the problem that is occurring.

              This is in CurrentSymbol. Replaces all

              Static string Symbol = " ":
              //per
              Static string SYMBOL; SYMBOL = CurrentSymbol ();
              
              //and also
              Static string Market = " ";
              //per
              Static string Market; Market = CurrentSymbol ();
              
              //and also (Left and Right operands of the conditions)
              (String) " ",
              //per
              (String) CurrentSymbol (),
              
              //And finally I added the code
              String CurrentSymbol (string symbol = "")
              {
                  Static string memory = " ";
                  If (symbol! = "") {Memory = symbol;} else
                  If (memory == "") {memory = Symbol ();}
                  Return (memory);
              }
              
              

              Solved my problem!

              Note: I compared and copied from my previous project.

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

                @tcanuto, I am doing something every day 🙂 I'm always careful not to break something, but the whole thing is very complex and sometimes problems happen.

                As usual I hardly understand what you are writing. What is the problem now, is it something in "Close Positions"?

                I told you this probably million times. But if you want to show me something, better show me some simple project that contains 2-3 blocks at most, so I can clearly see the problem. I'm lost in these big people's projects. You know your project, but I don't. I need time to first understand how the project works... and I am too lazy to do that unfortunately.

                1 Reply Last reply Reply Quote 1
                • tcanuto
                  tcanuto last edited by

                  As I said, the problem for me was in the lines of codes quoted above. But I changed manually in the mql5 code and it was ok.

                  Now you need to review the blocks containing the above codes. Once you review and correct what you need, let me know and I'll be generating a new project to test...

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

                    @tcanuto said in Bug in blocks:

                    As I said, the problem for me was in the lines of codes quoted above. But I changed manually in the mql5 code and it was ok.

                    Now you need to review the blocks containing the above codes. Once you review and correct what you need, let me know and I'll be generating a new project to test...

                    Complementing what I had said earlier: These changes I made in the code were based on the best results of my EA, but I'm not sure if it's the correct way to use it here in fxDreema.
                    In this case you should evaluate if the blocks need correction or not.

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

                    Online Users

                    M
                    S
                    T
                    O
                    G
                    B
                    A
                    P
                    I
                    M
                    M
                    J
                    T
                    S
                    T
                    M

                    30
                    Online

                    146.7k
                    Users

                    22.4k
                    Topics

                    122.6k
                    Posts

                    Powered by NodeBB Forums | Contributors