<![CDATA[Text input and Nubmer input add event at lost focus]]>It is posible, when input lost focus send like "@ti0 ABC" and "@ni0 123"

]]>https://forum.gui-o.com/topic/253/text-input-and-nubmer-input-add-event-at-lost-focusRSS for NodeSat, 11 Apr 2026 05:30:53 GMTSun, 02 Feb 2025 20:20:03 GMT60<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Sun, 09 Feb 2025 07:37:02 GMT]]>@kl3m3n
I tested an it works as excepted! Thanks 🙂

Best regards,
forest70

]]>https://forum.gui-o.com/post/1037https://forum.gui-o.com/post/1037Sun, 09 Feb 2025 07:37:02 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Thu, 06 Feb 2025 21:59:05 GMT]]>@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

]]>https://forum.gui-o.com/post/1034https://forum.gui-o.com/post/1034Thu, 06 Feb 2025 21:59:05 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Tue, 04 Feb 2025 21:45:42 GMT]]>@kl3m3n
Ok,
Thanks

]]>https://forum.gui-o.com/post/1031https://forum.gui-o.com/post/1031Tue, 04 Feb 2025 21:45:42 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Tue, 04 Feb 2025 21:04:10 GMT]]>@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

]]>https://forum.gui-o.com/post/1030https://forum.gui-o.com/post/1030Tue, 04 Feb 2025 21:04:10 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Tue, 04 Feb 2025 20:11:43 GMT]]>@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 🙂

]]>https://forum.gui-o.com/post/1029https://forum.gui-o.com/post/1029Tue, 04 Feb 2025 20:11:43 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Tue, 04 Feb 2025 15:05:12 GMT]]>@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

]]>https://forum.gui-o.com/post/1028https://forum.gui-o.com/post/1028Tue, 04 Feb 2025 15:05:12 GMT<![CDATA[Reply to Text input and Nubmer input add event at lost focus on Mon, 03 Feb 2025 20:05:05 GMT]]>@forest70 Hi,

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

Best regards,
Kl3m3n

]]>https://forum.gui-o.com/post/1027https://forum.gui-o.com/post/1027Mon, 03 Feb 2025 20:05:05 GMT