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

@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
OK, Tank you.

@gammda Fixed in v1.0.91.

Best regards,
Kl3m3n

@enniom Hi!

#1 - I agree with your suggestion. In the next release, the numbers will be displayed outside the actual chart area, live you've suggested.

#2 - This is strange - in your video I see GUI-O is receiving invalid characters (ABV%).
After you quit the application with the command, you then open GUI-O from "recent apps" and what do you do next? Your video does not show this. Do you connect to the device manually or you use auto-connection feature to re-connect automatically?

Can you try quitting only when all Bluetooth transmissions are complete and Bluetooth is disconnected?

Best regards,
Kl3m3n

@enniom Why are you setting ASR to 0.5, if no device has 0.5 ratio? Which is your development device?

Kl3m3n

@Sato I will update the example, so it is compatible with the new esp32 version.

@SteveV Hi.

Did you enter only the name or did you also specify the IP and port. All parameters must be specified...

If the tablet has WiFi, you can connect via "Ethernet". Please see my other answer here:
https://forum.gui-o.com/topic/198/could-the-gui-o-designer-be-made-to-work-with-wifi/2

True, "Ethernet" is usual terminology for internal wired connections. But in this case "Ethernet" means internal wireless connections. I think other (more technical) terminologies would be even more confusing for the user.

Best regards,
Klemen

@tgpa123 Hi.

I tested this on my device with ESP32 and can send longer data than 20 bytes. It seems that the server and client negotiate a larger MTU value in my case.

Nevertheless, I can chunk the data so that there is never more than 20 bytes by default. So, for messages greater than 20 bytes, multiple packets will be sent. Of course, the last packet will still be terminated with CRLF.

Regards,
Klemen

@kl3m3n

Again, thank you for the quick response!

Greetings!

@cayon Hi,

the bug should be fixed in v1.0.64.

Best regards,
Klemen

@pcu Hi!

I have made two examples using Nucleo board (USB and BLE).

You can find them here, if you are interested:
https://www.gui-o.com/examples/gui-o-and-boards/stm32-nucleo-wb55

Best wishes.
Klemen

@pcu Hi!

Thank you for pointing this out. I will put this on the issues list and fix it in the next release!
I will make it so that this functionality can be disabled in order to keep backwards compatible. I will check if there are any other widgets that behave in the same manner.

Regards,
Klemen

@kl3m3n

Android 13

Best regards,
Hub

@Bernard Hi Bernard!

Nice that you've solved the issue!

It would be very strange indeed if baud rate would affect the widgets responsiveness!

@Bernard said in Speed problems with Flick Area:

When switching from 9600 to 19200 baud, I also added "YASC:1" for the 2 graphs (SWEEP).

This is strange, sweep chart should support YASC parameter!
I will check this.

Regards,
kl3m3n

@Bernard Hi Bernard!

You are very quick to test new functionalities... 🙂

I have implemented auto-scaling in horizontal and vertical direction independently. Please replace "ASC" with "YASC". If you need to control scaling in horizontal direction, please use "XASC" (available for XY chart only).

I promise that the XASC and YASC parameters will not change in the future.

Best regards,
kl3m3n