GUI-O Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Disable Updates when editing a field

    Scheduled Pinned Locked Moved
    Wishlist
    2
    4
    500
    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.
    • T
      tgpa123
      last edited by

      I will try to explain this as an example

      Lets say a device is publishing updates live at some frequency, or when the value changes, to a number field. This field is also a setpoint, so the user can make changes. If you trying to change the value, and an updates is published from the device. It closes the user input.

      It might be an idea to disable field UI updates while editing the field. Could also notify user that the field has changed in the background.

      K 1 Reply Last reply Reply Quote 0
      • K
        kl3m3n @tgpa123
        last edited by

        @tgpa123 I will need to check this. If I understand correctly you would like a number field to be both indicator and control?

        I think this could potentially lead to usability issues due to not conveying clear meaning to the user... Is it a control or an indicator?

        Best regards,
        Klemen

        T 1 Reply Last reply Reply Quote 0
        • T
          tgpa123 @kl3m3n
          last edited by

          @kl3m3n

          Its not a critical thing, and there is ways to get around it. I just have setpoints that can be modified both at the device and via Bluetooth. I push change back to GUI-O app when the setpoint at the device changes. If you are changing settings on the app, it closes the window. This is just to keep setpoints/configuration up to date in the app.

          At the end of the day its a minor inconvenience and something that would rarely happen, but can. Not some much as a wish, as an idea..

          K 1 Reply Last reply Reply Quote 0
          • K
            kl3m3n @tgpa123
            last edited by

            @tgpa123 I understand.

            In my opinion, this is not a very transparent user feature - updating field from another source, while user is typing in the same field.

            I will put this on hold for now. If there should be a need for this feature in the future, I will consider it again.

            Best regards,
            Klemen

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