Posts made by 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

@forest70 Hi,

after some consideration, I think the loss of focus and not confirming the input should not send the command. This is counter-intuitive and is not standard behaviour of input widgets. User should be aware that they confirmed the input (e.g., by pressing Enter).

Can you explain what is your motivation for this? Maybe we can find another solution?

Best regards,
Kl3m3n

@forest70 Hi,

I will check if this can be reliably implemented.
I will get back to you.

Best regards,
Kl3m3n

@forest70 Hi,

currently, when widget is created it cannot be moved to another screen afterwards.

Best regards,
Kl3m3n

@jjl Hi,

you can now download the new designer version (v0.0.15), which also supports ITM functionality:

https://www.gui-o.com/design-tool

Best regards,
Kl3m3n

@jjl Hi,

yes it is. I need to add this to the designer.

Hopefully, I will do this during this weekend.

Thanks for pointing it out.

Best regards,
Kl3m3n

@devmonkey Version 1.0.93 is out.

Regards,
Kl3m3n

@devmonkey I used Arduino framework on top of mbed OS and i get pid 00C0, like you.

I have tested the GUI-O fix with Pico and it works.

Waiting for your feedback when new version of GUI-O is released (already in release process).

BR,
Kl3m3n

@devmonkey Thank you for pointing this out. I already created a fix. Testing now and will be releasing the version with the fix in the next couple of days (it usually takes Google a couple of days to review the app).

I will let you know.
Best regards,
Kl3m3n

@devmonkey Ok I will try this and get back to you.

@devmonkey Hi.

If you exit the GUI-O app and then plug in the Pico, what happens? There should be a pop-up window where you can select an app that can use the Pico device - is GUI-O shown on the list?

Can you try sending the data from Pico to GUI-O without GUI-O sending the @init string first? What happens then?

I also have an original RPi Pico and the Serial USB Terminal reports it as:
Serial device - CDC
Vendor ID:2E8A Name: Raspberry Pi
Product ID:000A Name: Pico

Can you tell me, where you got the Pico? Do you have a link of the store where you've ordered it from?

But I think the quickest way to get some additional information via adb (android debug bridge). I don't know how familiar you are with this, but I will describe the procedure (I will write for Linux, but the procedure for Windows is the same once you install adb):

1. Connect the device to your PC using USB cable
2. Navigate to Settings -> About phone -> and tab Build number / About phone 7 times
3. Go back to Settings and search for Developer options
4. Scroll down to debugging and enable USB debugging and then Wireless debugging
5. You should confirm authorization / pairing
6. Note the <ip_address> and <port>
7. On your PC, run the commands in the terminal (you need to be connected on the same WiFi network on your Android and your PC):

adb disconnect
adb tcpip <port>
adb connect <ip_address>:<port>

After connecting, remove the USB cable and use:

adb devices

You should see the Android device is connected.

Now run:

adb logcat > log_1.txt

This will start logging system messages to a file (named log_1.txt).

Now connect Pico to the Android device and start GUI-O. Try reproducing the issue with Pico and GUI-O. After you've finished this, press Ctrl+C in the terminal to stop the logging. Please send the file to: info.guio.app@gmail.com

Thank you.
Best regards,
Kl3m3n

@devmonkey Can you try the new version 1.0.92.

When creating a button widget, add the following property:

ITM:1

GUI-O will send data on button press and on release (you can distinguish the events by the received payload).

You can download the newest manual for more information.

Best regards,
Kl3m3n

@devmonkey Hi,

version 1.0.92 is out. Can you try and see if it works?

Best regards,
Kl3m3n

@devmonkey I have updated the usb library and added the device to the list of known devices (this should start GUI-O automatically when you plug in the device).

I will try to release a new version this week.

Best regards,
Kl3m3n

@devmonkey Hi,

I can add this functionality, yes.
Will add it with next version, with also updated usb serial library.

Best regards,
Kl3m3n