@Bernard Hi.

You can do one of the following:

Clear the app data from Android settings (settings - apps - GUI-O - clear all data). Note that this will clear everything, even stored devices.

Follow this link on GUI-O website:
https://www.gui-o.com/examples/gui-o-and-boards/esp32#h.7e5a31l59xj
Download the example and check the credentials in the code near the top. You can use port 8883 for secure communication, or 1883 otherwise. Client id can be empty, in this case GUI-O selects a unique generic client. You can also set it to your unique username.

Best regards,
Kl3m3n

@RudiP Hi.

I am fairly positive that settings are not the cause of this.

Can you first try changing the keyboard? I assume that your default keyboard is Samsung keyboard. Try changing it to Gboard (should be something like Android settings -> Additional settings -> Language and input).

Best regards,
Kl3m3n

@Bernard No problem!

I am glad it works now.

Regards.

@mile_hi_guy 👍

@mile_hi_guy Thanks for posting this. I have put this on my "issues" list.

Best regards.

@mile_hi_guy

Fixed, v0.0.20. Also added the comments to the selection view.
I made some minor changes and you will need to update your comments.

Best regards,
Kl3m3n

@mile_hi_guy Thanks for pointing this out!

Best regards,
Kl3m3n

@Vladì Hi,

version v1.0.110 now supports setting the default orientation. You can set it via the settings menu:
General settings -> Display settings -> Default screen orientation.

Best regards,
Kl3m3n

Thanks, I look forward to the fix.

My design if fairly complex. It sure would be helpful to be able to add comments to the box 2 command list. It seems to me adding a "comment widget" object would be a fairly elegant and simple way to enable this. The comment lines could then be displayed in box 2 and the GUI-O command string box. The comments would then be stripped out when sent to the GIO-O app.

@mile_hi_guy No problem.

I will try to make it more explicit in the next update (e.g., adding some meaningful text to "Connection lost because device stopped responding")...

I will also think about adding this feature to the designer app.

Thanks for the feedback.

Best regards,
Kl3m3n

@heromed

Hi Bob,

sorry for the late reply!

Wow, 65 years of experience... I can't even imagine all the challenges you've tackled over these years 🙂

Of course I can provide an "organized" list of all widgets along with their properties. What would be the best format for you?

One thing I still fail to understand - what will you use for the actual widgets on the editor canvas? Some more generic widgets?

Anyhow, I think we should move this discussion to an email or some other channel. If you want, you can send the reply to: info.guio.app@gmail.com

Best regards,
Kl3m3n

@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

@heromed

No problem. Glad you got it working.

Best regards,
Kl3m3n

@richamar Hi!

That's good to hear.

You can send messages in chunks if you want to, as GUI-O will process the command only when it receives "newline" character ('\n').

Best regards,
Kl3m3n

@jeremy0 Hi.

@kl3m3n said in Connection status?:

Connection monitor (separate for each connection type). If the feature is enabled, GUI-O app requires periodic messages (e.g., ping) after first received message. Otherwise, it will disconnect and enter error state. I will also support that the feature can be enabled from the controller command.

Implemented. See the latest manual, section Connection monitor.
I did not support enabling / disabling the connection monitoring via the commands. This can only be done in-app.

@kl3m3n said in Connection status?:

Any error that causes a disconnect will clear the UI.

Implemented.

@kl3m3n said in Connection status?:

Add support for @disconnect command. This will make it possible to send a disconnect request from the controller side. This will also clear the UI. User can then reconnect via the "Connect" button on top-left part of the home screen.

Implemented. See latest manual.

@kl3m3n said in Connection status?:

Add some sort of connected indicator when connected and on home screen (no UI loaded).

Implemented. A small indicator in the top-right corner of Connect button (home screen) shows if device is connected (green dot) or disconnected (red dot).

Best regards,
Kl3m3n

Exactly. The purpose is to reduce peak energy consumption values ​​and reduce costs.

@RudiP

I have prepared version v1.0.106 - you will be notified within the app when the upgrade is available. This version also fixes your issue.

If you feel like it, please support GUI-O and leave a feedback on the app store (please make sure you are not in the Beta testing program before giving feedback - you can tap on the Leave button):
https://play.google.com/store/apps/details?id=com.guio.guioapp

Best regards,
Kl3m3n

@RudiP No problem 🙂