@RudiP Hi!

I thought you meant using the "flashing" widget for non-communication purposes...

@RudiP said in auto flashing widget:

Since I currently have no communication via BT connection, this widget should flash independently.

Using an de-synchronized widget to show communication status is not a good idea. In case of communication loss, the widget would still flash, giving the user a wrong impression that the remote device still works...

If you need to show that the connection is established, your remote device should drive a widget periodically (e.g., toggling the visibility or opacity). Or you can use "@sls" and "@hls" commands that show / hide the loading screen.

@RudiP said in auto flashing widget:

I have an application where the processor is struggling to establish communication.

Can you explain what exactly you mean by this?

PS: I am glad you like the GUI-O app! Please consider rating it on the Google Play Store... Every rating helps 🙂

Best regards,
Kl3m3n

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

Best regards,
forest70

@kl3m3n
Thank you. Now it works.😊

Screenshot_20240703_160215.png

@kl3m3n Hi,
Thanks for reviewing my issue.
I have resigned to the fact that the cheapy ATMPC is probably not going to work with the 'ethernet' connection, and have taken on your suggestion to do the development on the Samsung and use the initialisation strings on the ATMPC.

I tried a test UI created on the Samsung using the GUI-O Live Designer, copied the initialisation strings into modified ESP32 code, created a new IoT device on the ATMPC and - Bingo! - worked a treat.

Thanks very much
Cheers
Steve

@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

@Hub said in Selectable language:

Hello @kl3m3n,

I can help with translation into Polish.

Regards,
Hubert

Thanks! 🙂
First, I need to prepare some stuff for this feature. I will let you know.

@Hub Hi!

What about using |TI (text input) widget? I can probably add some validators to ensure the entered text is HEX.

Regards,
Klemen

@kl3m3n Excellent, I look forward to it!

@kl3m3n
Sweet! No more nightmares about jumbled text columns 😉

Thank you! I happily left you ***** on google play.

Greetings.

@kl3m3n
Nice, thank you

@enniom Thank you. 😁

Hi !
Strange, indeed !

Same problem when setting Serial.Begin(9600) beside of Serial.begin(115200) in BasicUSB code

(On LOLIN S2 mini Serial is USBCDC Serial, Baud may be changed , not frame )

I Will test another ESP-32 board, TTGO one, with USB connector switchable between UART w CH340 and native USB

No special tuning with Serial USB Terminal anc BasicUSB code , ok with 115200 or 9600bauds, ESP answer to @init is OK.

Best Regards,
Alain

@al1fch Hi!

Thank you for the support and kind words.

Regarding the iOS... I sincerely hope there will be an iOS version available somewhere in the near future. That is the plan, but... As I am a single developer of GUI-O application as well as GUI-O designer (not to mention all of the website content, etc.) and doing all this in my free time, it will probably take some time. Honestly, I cannot give you even the rough timing estimate.

There are some challenges "porting" GUI-O application to iOS.

Since majority of the application is written in C++ (I believe that clang compiler for iOS allows mixing C++ and Objective-C), this would be the "easier" part. There is some Android Java code which would need to be re-implemented.

But, as I see it, the most difficult part is the setting up the development environment. Installing Xcode on a non Apple PC is a pain. I believe newer Xcode versions don't even work with older Mac's, and buying a Mac computer costs a small fortune. I have tried running Xcode on a virtual Mac OS with unsatisfying results.

I apologize I cannot give you a better answer at this moment.

Best regards,
kl3m3n

@sato said in Timestamp through Gui-o MQTT server:

Hello,
If there is also a possibility, when connected to the Gui-O MQTT server, to be able to receive, whenever requested, the Timestamp, without the need to have a Gui-O APP open?

If so, how to do that?

Regards
Fernando

Hello Fernando.

The MQTT protocol by itself does not include a timestamp, so you would need to create the timestamp on the client side.
You could also have a reference device (could also be a PC) that publishes the timestamp to some topic. You can then subscribe to this topic on your microcontroller.

Best regards,
kl3m3n

Hello!

You mean like a boolean flag to enable / disable date time prepending to each line in a file. For example:

[date_time] text [date_time] text2 ...

when flag is enabled and

text text2 ...

when flag is disabled?

Can you confirm this?

Thanks.

Implemented in v0.11.4 (already available).

Added touch response to image and video widgets. Touching the image (video) widget now sends the message in the following format: @<uid>, where <uid> denotes the widget's unique identifier set by the UID: parameter.