@richamar Hi!
Can you please show a simple command, so I can try to reproduce this.
If the widget appears on the top of the screen (at 0 position), then the given Y position is invalid. Can you please check that there are no spaces between parameter and payload, e.g.:
Y: 50
It should be:
Y:50
You can output the data to serial for debugging, before sending it to BLE...
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
@jeremy0 Hi,
the main aspect of GUI-O is to be as generic as possible. So with this in mind, I will add the following features:
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.
Any error that causes a disconnect will clear the UI.
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.
Add some sort of connected indicator when connected and on home screen (no UI loaded).
BTW:
May i suggest that you create an indicator that you periodically toggle from the controller side. This way, you will know when connection is active.
Best regards,
Kl3m3n
@jeremy0 Hi
Thank you for the detailed explanation. If you can do more tests, that would be great! If I can reproduce your issue I will be able to solve it more quickly.
Meanwhile, I will think about how to improve the user experience in such cases. I can't remember exactly, but I think that I wanted to keep the UI after error for some reason.
BTW: The ping idea seems a valid proposition. I could add an option to enable a "heartbeat" message, which would then use the current @ping -> @pong functionality. The app will expect a periodic ping from the controller (after receiving first message) and send a response - just like now, but it would also disconnect with an error message if ping is not received within the specified interval.
If you enable autoconnect, GUI-O will try to periodically re-establish the connection. Without autoconnect, it just latches the error.
@jeremy0 said in Connection status?:
(And while I think of it: I can't see a way to return to the main menu screen from a UI page, other than having the target issue @quitapp in response to a button press - which is great, but only works if the target is connected and responsive. The rest of the time I have to actually switch away from the app altogether and relaunch it.)
Try swiping from the left to right (edge of screen) to open the settings menu. Then press the "home" icon on top-right of the screen. This will clear the UI and return you to the "home screen".
Best regards,
Klm3n3
@jeremy0 Hi!
In TCP connection, GUI-O is the client and should detect disconnection from the server. Furthermore, if "autoconnect" is enabled it should periodically try to reconnect.
Can you give more information about your setup, so i can try to reproduce the issue you are describing?
Best regards,
Kl3m3n
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 Hi Rudi,
yes, you are right - the drop down box does not support spaces.
The DAL parameter does not support spaces (for LST, TU and DRB widgets).
I will see if I can fix this.
Best regards,
Kl3m3n
@RudiP Hi Rudi,
can you explain a bit more? Please give an example of what you are trying to do.
GUI-O supports spaces from its initial release in all text fields. It also supports some more advanced outputs...
Best regards,
Kl3m3n
@RudiP said in MBCH koliko label in podatkov lahko pokažem:
Hi Rudi,
please write in English, so others can understand more easily. You can use Google Translate or ChatGPT to translate your text to English.
I translated your text, but please in the future try to use English.
How do you know that MBCH only allows 5 values and 5 labels? Did you try initializing it with 7 values and 7 labels, for example:
"|MBCH UID:mbch0 X:50 Y:50 MCHV:\"1,4,9,16,25,36,49\" MCHL:\"bar0,bar1,bar2,bar3,bar4,bar5,bar6\"\r\n"
Best regards,
Kl3m3n
@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 Ok, thanks.
I have implemented local purchases caching (supported for Android 6 and above). The data is encrypted and persists through upgrades, but not re-installing the app.
I need to test this a bit more and then I will release the update.
Can you tell me if there is any notification (toast) message when GUI-O reverts back to DEMO version? Or just displays "Demo version" on the home screen?
Best regards,
Kl3m3n
@somasundaram-i Hi,
you don't need to clear the GUI-O app data, only Google Play Store data.
But still, this is a strange behavior.
Can you please tell me:
Google Play Store should cache the purchase data - I think none of the users reported any errors regarding this. But now I am thinking about implementing offline (in-app) caching of purchase state.
Just waiting for your details, so that I can see if there is something else wrong with this.
Thanks.
Best regards,
Kl3m3n
@somasundaram-i
I am glad it works. 
Did you perhaps leave the Beta testing recently as I've mentioned in one of the above posts?
I would still like to get to the bottom of this. Do you have another account on the same device?
Best regards,
Kl3m3n
@somasundaram-i
Do you by any chance know, which version were you using before the upgrade to 1.0.103?
@somasundaram-i Hi!
I am sorry for the inconvenience.
Can you please tell me, which GUI-O version do you have?
Can you try rebooting the device? If this doesn't work, can you clear the Google Play Store app cache? Navigate to Android Settings > Apps > Google Play Store > Clear data > Clear cache.
Also try re-installing the GUI-O app.
Can you try GUI-O on another device, using the same account?
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:
This image represents an image with 1280x720 resolution:
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
If you have the version 1.0.98 or below it should work ok.
Otherwise, you can wait foe version 1.0.103, which will be released in a day or two.
The version 1.0.98 is the latest production version. If your version is higher, you are enrolled as a beta tester. You can leave the beta testing via the Playstore GUI-O page (at the bottom). You then need to remove and reinstall the app. This way you will only get production versions when they are ready.
Best regards,
Kl3m3n
@somasundaram-i Hi,
can you please tell me, which app version you have?
I see this problem on the newer versions.
If you just rotate the screen with the "rotate" command, is GUI-O background (with the initialization button) extending over the entire screen or just a part of the screen?
Thanks.
Best regards,
Kl3m3n