@Hub

I am happy you find the improvements useful!

Thanks.

Regards,
Klemen

@SteveV Hi!

You mean you cannot enter IP address due to not having any period ('.') character available?

This is not normal. Can you try changing the keyboard from Android settings and see if the issue persists?

I am "forcing" the number keyboard when user touches the IP field... In most cases, the keyboard also shows other characters. Anyway, I will fix this ASAP - I have a release lined up right now. I will probably take a day or two...

Best regards,
Klemen

@Bernard Yes, you have wrong credentials. This is what's causing the problem. You have changed the settings somehow...

I advise you to clear application data or uninstall and reinstall the application. This will reset the settings to default. Alternatively, you could input the correct settings, but I recommend reinstall... It will be easier for you. Then retry pairing.

Note that you must keep the default settings if you want to connect to GUI-O server!

Best regards,
kl3m3n

Hi!

Ok, I understand!

@Sato said in On close with > clear some flags:

If Guio loses its internet connection, after a short time the Esp restarts and all the flags are cleared.

How does the ESP know to restart if GUI-O loses connection?

@Sato Hi,

which connection type are you using?

If you are using MQTT, and you have a bad connection, the "exit" action could actually take longer and the app may seem unresponsive to the user. This is not a good solution.

What do you do if GUI-O suddenly losses internet connection? How do you clear the flags then?

Kl3m3n

@Sato Hi!

I am great, thank you. What about you?

I assume you want to clear the flags on the microcontroller side? So, on your microcontroller side, just clear the flags on disconnect (Bluetooth, some USB connections).

In MQTT it's a bit trickier, but you can send periodic ping to the app (using @ping command). When there is no reply after, for example, 3 ping requests, you clear the flags.

Delaying the exit in order to send a message is not a good approach in my opinion as the app could seem unresponsive.

Best regards,
Kl3m3n

@kl3m3n The issue should now be fixed.

You will need:

• GUI-O version 1.0.97 (should be released today or tomorrow)
• Designer tool version 0.0.17 (already released)

Best regards,
Kl3m3n

@Fred-Neuman said in Gui-0 Live Designer V0 .0.16 - Transfer to Device:

Gui-0 Live Designer V0 .0.16 - Transfer to Device
The command “transfer to Device’ is quite useful to transfer a design toward android device:
\Android\data\com.guio.guioapp\files with the PRO version.

It works fine with Widget that has no customisation (with default value) since the data sent is shorter. Although If I customize a widget with some features, it add some double quotes and backslash to the Widget parameters. In my case it prevents the Transfer to my Device Samsung. Example for Spinnable list Widget:

|TU UID:tu3 X:50 Y:50\r\n - Transfer to Device works fine

|TU UID:tu0 X:18 Y:55 FGC:#FF0000 FSZ:5 DAL:"2,3,5,7,9,11,13, "LI:2\r\n"

• Won’t transfer to Device - I suspect \” Li to be the cause

I would say that the issue occurs with others Widgets, but i did not make a test on everyone
Regards

Hi,

sorry for being quiet for so long.

I have checked this and the problem seems to be when using parameters that expect internal quotes (e.g., DAL:"2,3...").

Since the "transfer to device" feature uses the EXTF component (file read / write) of the GUI-O, the problem lies there.
I will try to fix this issue ASAP.

Best regards,
Kl3m3n

@Fred-Neuman Thanks for pointing this out! I will check this and let you know.

Best regards,
Kl3m3n

@Fred-Neuman v0.0.16 also includes this fix.

Best regards.

@Fred-Neuman Hi!

Please remove the \r\n from the end as the GUI-O designer already does this internally.

On the next release, I will fix this, so it will not matter.

Best regards,
Kl3m3n

@forest70 Hi!

I have fixed the ACT issue.
The new version should be available in Play Store in a couple of days.

Best regards,
Kl3m3n

@forest70 Hi Davor,

this seems to be a bug.

I will fix it with the next release!

Thank you for reporting this.

Best regards,
Kl3m3n