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

Text input and Nubmer input add event at lost focus

Scheduled Pinned Locked Moved
Wishlist
2
8
426
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.
  • F
    forest70
    last edited by 2 Feb 2025, 20:20

    It is posible, when input lost focus send like "@ti0 ABC" and "@ni0 123"

    K 2 Replies Last reply 3 Feb 2025, 20:05 Reply Quote 0
    • K
      kl3m3n @forest70
      last edited by 3 Feb 2025, 20:05

      @forest70 Hi,

      I will check if this can be reliably implemented.
      I will get back to you.

      Best regards,
      Kl3m3n

      1 Reply Last reply Reply Quote 0
      • K
        kl3m3n @forest70
        last edited by 4 Feb 2025, 15:05

        @forest70 Hi,

        after some consideration, I think the loss of focus and not confirming the input should not send the command. This is counter-intuitive and is not standard behaviour of input widgets. User should be aware that they confirmed the input (e.g., by pressing Enter).

        Can you explain what is your motivation for this? Maybe we can find another solution?

        Best regards,
        Kl3m3n

        F 1 Reply Last reply 4 Feb 2025, 20:11 Reply Quote 0
        • F
          forest70 @kl3m3n
          last edited by 4 Feb 2025, 20:11

          @kl3m3n
          Edit field, click on confirm, keybord is closed, click on next field, keyboard is open ... anoing.
          It is simple, there are some field of input. Edit first, click to second an so on.
          So lost focus can be a solution, or is there command to ask field value.

          Best regards,
          forest70
          PS
          V slovenščini bi šlo lažje 🙂

          K 1 Reply Last reply 4 Feb 2025, 21:04 Reply Quote 0
          • K
            kl3m3n @forest70
            last edited by 4 Feb 2025, 21:04

            @forest70 Hi,

            I see... This can be annoying, yes.
            Both options you propose seem interesting (focus and value query). I will think about this and perform some tests with GUI-O, to see what works best.

            Best regards,
            Kl3m3n

            PS: Najbrž res, a potem ostali ne bodo razumeli 😄. Lahko pa v SLO rečeva kakšno na direktnem sporočilu. Je pa vseeno bolje debatirati tukaj, morda še komu tale debata pride prav

            F 1 Reply Last reply 4 Feb 2025, 21:45 Reply Quote 0
            • F
              forest70 @kl3m3n
              last edited by 4 Feb 2025, 21:45

              @kl3m3n
              Ok,
              Thanks

              K 1 Reply Last reply 6 Feb 2025, 21:59 Reply Quote 0
              • K
                kl3m3n @forest70
                last edited by 6 Feb 2025, 21:59

                @forest70

                I decided to add an option to request the current value / state of (specific) widgets. This seems a better solution compared to sending the data on lost focus.

                The new version will be released in a couple of days and I will also update the manual.

                Basically, you just need to send:

                @<widget_uid> REQV:1\r\n
                

                This will return the current value / state for the widget (in the same format as with user interaction).
                You can retrieve the values of the TI and NI fields on demand.

                Best regards,
                Kl3m3n

                F 1 Reply Last reply 9 Feb 2025, 07:37 Reply Quote 0
                • F
                  forest70 @kl3m3n
                  last edited by 9 Feb 2025, 07:37

                  @kl3m3n
                  I tested an it works as excepted! Thanks 🙂

                  Best regards,
                  forest70

                  1 Reply Last reply Reply Quote 1
                  5 out of 8
                  • First post
                    5/8
                    Last post