fxDreema

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

    Condition Bug?

    Bug Reports
    3
    5
    1278
    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.
    • V
      vnpython 0 last edited by

      i am using chrome and working on the project and suddenly see some strange behavior on the condition as follows:

      1. drag 1 condition and open property as below
        0_1538902296956_20181007_154814.jpg
      2. drag another condition and open property as below
        0_1538902355228_20181007_154829.jpg
      3. now play around with the operator (more than, less than, x up, x down) and u see the crosswidth appear and off but it wont go away even after you settle on operator do not need crosswidth
        0_1538902467362_20181007_154848.jpg
        so do i get 1 or 2 day (depends how long) of subscription while waiting for this 'bug' to iron out? i fear with this bug may mess up the strategy?
      1 Reply Last reply Reply Quote 0
      • V
        vnpython 0 last edited by

        @fxDreema please check Sir?

        1 Reply Last reply Reply Quote 0
        • D
          Daniel95 last edited by

          I have this Problem also in Firefox. Did you check it in MetaEditor? Maybe its just a bug in FxDreema.

          1 Reply Last reply Reply Quote 0
          • V
            vnpython 0 last edited by

            this only happens when 2 condition panel is opened. the selection on the newly opened will cause the first panel to react. if open individually, no such issue. for safety sake, i re-open the conditions one by one and check. after checking, the EA runs fine. before that was unable to do as designed...

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

              I know this bug, it is just a visual bug. That input sits there all the time, but it goes visible when it doesn't need to. But "cross width" is something that nobody uses anyway. I know only 1 case when someone really needed it, and it was years ago. Don't be afraid of it, it doesn't break anything.

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

              Online Users

              A
              R
              S
              M
              P
              R
              A

              21
              Online

              146.7k
              Users

              22.4k
              Topics

              122.6k
              Posts

              Powered by NodeBB Forums | Contributors