@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