Touch functionality not responding for Fenix7/7pro

CIQ data fields can't accept touch input on watches, only Edge devices. I'm surprised that it works for Venu 2 Plus and FR965.

Can you elaborate on exactly what touch functionality you are referring to? If you mean touch input in on-device settings, I think that would be an exception to what I said above. But the CIQ data field view itself should not be able accept touch input on watches, afaik.

Yeah, then I would've expected it not to work on any watch.

The fact that it does seem to work on some watches would be an unexpected bonus to me.

Unfortunately it's not very well documented. (I'm struggling to even find official Garmin documentation that mentions this limitation, which is supposed to be "well known". It's been mentioned in the forums many times though.)

Does onTap() work for your data field in the simulator, for venu2plus and fr965?

I have never managed to test onTap() in the simulator with the watches. The function is not being called.

Just to make sure I'm not imagining things :) I'm testing the data field on the actual Venu2plus. I can confirm that it works and responds correctly when I tap on the corresponding data field active areas.

Wow that's crazy.

Def sounds like bonus functionality. Maybe we should delete this thread before Garmin notices 

Going back to this old discussion, it's possible that this limitation was never officially documented:

https://forums.garmin.com/developer/connect-iq/f/discussion/7392/datafield-ontap/49924#49924

Travis.ConnectIQ said:

I'm almost certain that this is not something that is supposed to work with wearables, even the ones that support touch like the vva3/m. I see that an issue has been filed, so maybe that will change.

Maybe this has finally changed. If so, I think at the very least:

- it should be formally documented (including listing the devices which are supposed to support this functionality)

- the simulator should match the real device

It would be nice to have some clarification from Garmin regarding the expected behavior on each watch.

Hi Iñigo!

After updating F7Pro to FW v.20.10 the data field can't connect to H10 anymore. Already post it to bug section.

Also, I just tried this on my fr955 (running beta 22.12) and it works! (onTap() is invoked in a CIQ data field when I tap the field)

Thanks for posting this!

peterdedecker

I think this is functionality you wanted for a long time - the ability for a data field to accept input on a watch, although it would be nice if it wasn’t just onTap() for a limited number of watches. I don’t think it would be feasible to build a data field that revolves around accepting input (*), but at least finally there’s a way to accept input as bonus functionality. 

(*) Unless:

- all devices/firmware which support onTap() in a data field can be identified

- the app description documents that it requires touch (no problem for touch-centric devices like Vivoactive and Venu which are severely crippled when touch is disabled, but perhaps a problem for 5-button watches where 99% of the functionality — especially all the important functionality — works without touch.)

Can you test if DeviceSettings.isTouchScreen returns true in the datafield? And if yes, then does it return false if you disable touch for the activity? That way at least we could do things like: if touch enabled then switch "page" (displayed data) and if disabled then switch page every 3 seconds.

flocsy🤠 said:

Can you test if DeviceSettings.isTouchScreen returns true in the datafield? And if yes, then does it return false if you disable touch for the activity?

This sounds like something you could easily test yourself tho.

Based on the documentation, the correct answer (not necessarily the actual answer) to both of those questions should be "yes".

https://developer.garmin.com/connect-iq/api-docs/Toybox/System/DeviceSettings.html#isTouchScreen-var

flocsy🤠 said:

if disabled then switch page every 3 seconds.

This doesn't sound very user-friendly to me. Any sort of "auto-scroll" functionality should be opt-in, in my opinion (based on the principle of least surprise). (To me, disabling the touchscreen doesn't count as opting-in to having a random CIQ data field constantly flip pages.)

As an example, I've seen several threads in the forums from users who wondered why their data pages started changing for no apparent reason - turns out they enabled ClimbPro and were not aware that part of the feature is to change your data page when you start climbing. And this feature is disabled by default, so users have to explicitly enable it (but ofc obviously some are unaware of the data page switching aspect of the feature).