Topics created by RudiP

@RudiP Hi!

No, your initialization is not the problem.

I will try to find out the cause why the canvas is not being pushed up. First, I need to reproduce the error.

I will let you know about further developments.
Thanks for your patience.

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

@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.😏

@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