@Hub

I am happy you find the improvements useful!

Thanks.

Regards,
Klemen

@SteveV Hi!

You mean you cannot enter IP address due to not having any period ('.') character available?

This is not normal. Can you try changing the keyboard from Android settings and see if the issue persists?

I am "forcing" the number keyboard when user touches the IP field... In most cases, the keyboard also shows other characters. Anyway, I will fix this ASAP - I have a release lined up right now. I will probably take a day or two...

Best regards,
Klemen

@Bernard Yes, you have wrong credentials. This is what's causing the problem. You have changed the settings somehow...

I advise you to clear application data or uninstall and reinstall the application. This will reset the settings to default. Alternatively, you could input the correct settings, but I recommend reinstall... It will be easier for you. Then retry pairing.

Note that you must keep the default settings if you want to connect to GUI-O server!

Best regards,
kl3m3n

@Vladì Hi.

Did you install the GUI-O from the same account (are there any other accounts on the tablet)?

Try this one by one...

1. Make sure the correct account is selected in Play Store:

• Play Store → Profile → Payments & subscriptions → Purchases

2. Try clearing the Play Store cache and rebooting the device after:

• Settings → Apps → Google Play Store
• Tap Storage
• Tap Clear cache

3. Re-install the app.

Please tell me how this goes.

Best regards,
Kl3m3n

@Vladì Hi!

The license is tied to the Google account, so if you are using the same account on your tablet, it should work.

Regards,
Kl3m3n

@heromed Hi,

Q0 error means that the connection was refused. This error probably comes from the TCP transport layer. The server application did not accept the connection at the socket level due to some reason (wrong port or wrong address family)...

Can you try using another app (just to test) to try connect to GUI-O designer tool. For example:
https://play.google.com/store/apps/details?id=com.sollae.eztcpclient

Regards.
Kl3m3n

@heromed Hi!

I assume you followed the instructions here:
https://www.gui-o.com/design-tool#h.l8bfgce9xopc

Did you provide the IP address of the Wireless adapter (not for example Ethernet adapter)? In my case:

Also - is your firewall blocking the designer app?

Best regards,
Kl3m3n

If GUI-O has helped your projects or saved you time, you can optionally support its continued development.

Support is completely optional. Using GUI-O does not require any contribution.

Thank you to everyone who uses, tests, reports issues, or shares feedback - this support already means a lot.

@richamar Hi!

That's good to hear.

You can send messages in chunks if you want to, as GUI-O will process the command only when it receives "newline" character ('\n').

Best regards,
Kl3m3n

@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