@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 🙂

This website is not valid:
84d019e0-7241-4022-807b-71420e4d6b9f-image.png

I suggest you use:

BT.print("|TI UID:ti_Https X:50 Y:15 W:100 BGC:#FFC000 FGC:#000000 SHC:#FFC000 TXT:"https: " SCI:0\r\n");

SCI:4 means 5th screen.😏

@somasundaram-i Please try version 1.0.104, when it becomes available (you need to be in a beta tester program).

I would appreciate some feedback, when you test it.

Best regards,
Kl3m3n

@somasundaram-i Your were missing the position. When you create a widget, the position is mandatory. Please check the manual.

Best regards,
Kl3m3n

@somasundaram-i Hi,

I tried reproducing the issue on 1280x720 emulator and everything seems to work fine.

This image represents an image with non 1280x720 resolution, stretched to the entire available screen:

1280x720_image.png

This image represents an image with 1280x720 resolution:

1280x720_image2.png

The GUI-O init command is:

|IM UID:im0 X:50 Y:50 W:100 H:100 IP:"<image>" SCM:1\r\n

Best regards,
Kl3m3n

Hello @kl3m3n,

Works very good, Thank You

Best regards

Hello @kl3m3n,

I understand, thank you

Best regards

@RudiP Hi!

Thanks for reporting the issue. To help diagnose the problem, could you please provide a minimal example where this happens? Specifically, I’d like to see the widget initialization code that triggers the problem.

Also, what is the make and model of your Android device? If it’s an older or lower-end device, the issue might be related to limited system resources like RAM or GPU memory. Initializing complex widgets with a lot of data can sometimes cause delays or rendering issues on such devices.

Lastly, does the app crash or freeze, or is the screen just black but still responsive to touches?

Best regards,
Kl3m3n

@Sato I am glad to hear that! 🙂

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 v0.0.16 also includes this fix.

Best regards.

@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

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

Best regards,
forest70