@mile_hi_guy 👍

@mile_hi_guy Thanks for pointing this out!

Best regards,
Kl3m3n

@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

No problem. Glad you got it working.

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

@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

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

@Bernard Very nice! 🙂 It is always a good feeling when you solve a problem yourself! 👍

@kl3m3n - This confirms my understanding of the documentation.
This would be a convenience for me, especially while developing my app. But I have found the workarounds that you mention.

I suspect that there would be situations where I would like to do something on the client side without round-tripping to the source. Like touching a point on a chart and seeing the nearest measured value. But at this moment I don't have a crucial need.

I do see how local callbacks on the client side might complicate the tool and conceivably create security issues.

Dave

@kl3m3n Thanks for your answer. Yes this is (micro)python, used on an ESP32.

@Bernard

@sls 500 - Request to hide loading screen. This means that all widgets will appear on the screen at the same time.
If you have many widgets in the Init procedure without this command, you may see each one being installed separately, especially if a low baud rate is used.
At the end of the initialization process must be @hls 10 The number means how long in ms the animation is displayed

These commands are useful when reinitialization happend. If you don't clear GUI-O widgets, they are duplicated and doesn't display properly.
@cls - clear the screen
@clh - clear all hardware components
@clo - clear orientation - when you want to set the screen to the default orientation

@gse - this is a general setting (specify the delimiter character COD:0 - space, COD:1-coma TSC:39 means " ' " delimiter on i.e. TXT
@guis - screen definition

I usually use this:

@sls 200 @cls @clh @gse COD:0 TSC:39 @guis BGC:#000000 ASR:0.4486 .... @hls 10

ASR:0.4486 is screen ratio for Samsung A13,
BGC:#0000000 means black background on home screen.

@kl3m3n

Thank You

Regards
Fernando

@kl3m3n

Thank you for the explanation

Best regards

Hello,

you can create both widgets with one invisible (or opacity set to 0):

VIS:0 or OPA:0

Then you delay on the microcontroller side and send the VIS:1 or OPA:1 command when the delay expires. This will then show the widget to the user.

Hope this helps.
Best regards.