Posts made by kl3m3n

@heromed

Hi Bob,

sorry for the late reply!

Wow, 65 years of experience... I can't even imagine all the challenges you've tackled over these years

Of course I can provide an "organized" list of all widgets along with their properties. What would be the best format for you?

One thing I still fail to understand - what will you use for the actual widgets on the editor canvas? Some more generic widgets?

Anyhow, I think we should move this discussion to an email or some other channel. If you want, you can send the reply to: info.guio.app@gmail.com

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 Hi!

This is a good idea. It would make sense for some widgets to support blinking. I will think about it.

Which widget do you have in mind? Currently, you can blink any widget by toggling its visibility. Did you try it?

Best regards,
Kl3m3n

@heromed BTW - If you like GUI-O app, please consider leaving a review on Google Play Store.

Thanks.
Kl3m3n

@heromed Hi!

No offense taken regarding the current design tool. I strongly agree that it is not very user friendly...

The initial plan was to introduce a simple designer, which would then gradually "grow" into a more capable, user friendly graphical editor.

But, maintaining the GUI-O app (and basically everything else related to GUI-O), I never got this far. It is not a simple project anyhow.

To answer your questions:

It is definitely worthwhile from GUI-O perspective as it would surely be a significantly more friendly tool to create layouts. From my point of view, I see no problem if you license the editor as a FreeWare.

I only see one problem if you go ahead with this - almost all widgets are custom (low-level paint operations), which means all the logic is implemented in the GUI-O. So in order to create an editor that will be 1:1 compatible with GUI-O, you would need to re-implement the widgets exactly... Ideally, the codebase for the widgets should be the same (e.g., shared between the GUI-O app and the editor).

I am sure you understand I cannot share the source code for this as this is one of the main features of GUI-O.

Can you share a brief overview on how would you implement the editor? So we can discuss this further.

P.S.: Which app did you develop? Can I download it from Google Play Store?

Best regards,
Kl3m3n

@heromed

No problem. Glad you got it working.

Best regards,
Kl3m3n

@heromed Hi.

Does the Python client run locally?

If it does, it may bypass some network or security restrictions, which could explain why it works. I still think this could be some Windows misconfiguration. Do you have any antivirus or endpoint security software running that might be blocking incoming connections?

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

@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

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