@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

@Fred-Neuman said in Gui-0 Live Designer V0 .0.16 - Transfer to Device:

Gui-0 Live Designer V0 .0.16 - Transfer to Device
The command “transfer to Device’ is quite useful to transfer a design toward android device:
\Android\data\com.guio.guioapp\files with the PRO version.

It works fine with Widget that has no customisation (with default value) since the data sent is shorter. Although If I customize a widget with some features, it add some double quotes and backslash to the Widget parameters. In my case it prevents the Transfer to my Device Samsung. Example for Spinnable list Widget:

|TU UID:tu3 X:50 Y:50\r\n - Transfer to Device works fine

|TU UID:tu0 X:18 Y:55 FGC:#FF0000 FSZ:5 DAL:"2,3,5,7,9,11,13, "LI:2\r\n"

• Won’t transfer to Device - I suspect \” Li to be the cause

I would say that the issue occurs with others Widgets, but i did not make a test on everyone
Regards

Hi,

sorry for being quiet for so long.

I have checked this and the problem seems to be when using parameters that expect internal quotes (e.g., DAL:"2,3...").

Since the "transfer to device" feature uses the EXTF component (file read / write) of the GUI-O, the problem lies there.
I will try to fix this issue ASAP.

Best regards,
Kl3m3n

@Fred-Neuman Thanks for pointing this out! I will check this and let you know.

Best regards,
Kl3m3n

@Fred-Neuman v0.0.16 also includes this fix.

Best regards.

@Fred-Neuman Hi!

Please remove the \r\n from the end as the GUI-O designer already does this internally.

On the next release, I will fix this, so it will not matter.

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

@forest70 Hi Davor,

this seems to be a bug.

I will fix it with the next release!

Thank you for reporting this.

Best regards,
Kl3m3n

@Proto Hi!

Yes, you need a license for each Android device that uses a different Google account from the one used to purchase the license.

Licensing is based on the app, not on development. Specifically, the app does not track (and cannot enforce) which device is designated as the "development" device.

Best regards,
Kl3m3n

@forest70

I decided to add an option to request the current value / state of (specific) widgets. This seems a better solution compared to sending the data on lost focus.

The new version will be released in a couple of days and I will also update the manual.

Basically, you just need to send:

@<widget_uid> REQV:1\r\n

This will return the current value / state for the widget (in the same format as with user interaction).
You can retrieve the values of the TI and NI fields on demand.

Best regards,
Kl3m3n

@jjl said in Button released events:

@kl3m3n Hi

Have not seen the new release until now.
The Live designer did not mention anything about a new release !!

New release works fine. Great work,

Thanks.

/Jens

Yes, there was a bug in the previous release regarding the version check...

Thanks

Best regards,
Kl3m3n

@forest70 Hi,

I see... This can be annoying, yes.
Both options you propose seem interesting (focus and value query). I will think about this and perform some tests with GUI-O, to see what works best.

Best regards,
Kl3m3n

PS: Najbrž res, a potem ostali ne bodo razumeli . Lahko pa v SLO rečeva kakšno na direktnem sporočilu. Je pa vseeno bolje debatirati tukaj, morda še komu tale debata pride prav