Forerunner265/265s and onDrag

One thing to keep in mind is not all touch device support onDrag.  Here is the list of supported devices from the API doc:

Supported Devices:

[Hide devices]

• Approach® S70 42mm
• Approach® S70 47mm
• Captain Marvel
• D2 Air X10
• D2 Mach 1
• Darth Vader
• Edge® 1030 Plus
• Edge® 1030
• Edge® 1040 / 1040 Solar
• Edge® 830
• Edge® 840 / 840 Solar
• Edge® Explore 2
• epix (Gen 2) / quatix® 7 Sapphire
• epix Pro (Gen 2) 42mm
• epix Pro (Gen 2) 47mm
• epix Pro (Gen 2) 51mm
• fēnix® 7 / quatix® 7
• fēnix® 7 Pro
• fēnix® 7S Pro
• fēnix® 7S
• fēnix® 7X / tactix® 7 / quatix® 7X Solar / Enduro 2
• fēnix® 7X Pro
• First Avenger
• Forerunner® 955 / Solar
• Forerunner® 965
• MARQ® (Gen 2) Athlete / Adventurer / Captain / Golfer
• MARQ® (Gen 2) Aviator
• Rey
• Venu® 2 Plus
• Venu® 2
• Venu® 2S
• Venu® Sq 2 Music
• Venu® Sq 2
• Venu® Sq. Music Edition
• Venu® Sq
• Venu®
• vívoactive® 4
• vívoactive® 4S

Devices without touch don't, and in cases like the fr955 and fr965, the watches have settings to disable touch.

Yeah, that's what I found out but it's still odd that the Forerunner 265 and 265s are left out. They are touch screen just like the others and also on ICQ 4.2.0. Even watches released before it like the Venu2 has it and even its big brother the Forerunner 965. Why was the 265 left out? It seems to be the only recent touch screen device without drag support.

Has anyone tried this on a real 265?  With the latest (beta?) FW? It could be the doc and sim is wrong.  The doc doesn't have the venu3/3s or va5, but the sim shows it's there on them.

I was contacted by a user saying my calculator app wasn't working on his 265s. I use the onDrag call instead of onSwipe because my app reacts differently depending where you swipe on screen. That's when I noticed the 265 aren't supported devices and made this thread.

SylvainGa said:

That's when I noticed the 265 aren't supported devices and made this thread.

I'm curious whether the 265 supports dragging natively. I would be very surprised if it didn't, but I can think of a way a user could test for you.

When I drag a watchface, glance, data page or other native UI element on my 955 (which does support onDrag), the element follows my finger precisely. This can be seen, for example, if I open an activity (with multiple data pages), and drag a data page halfway without letting go of the screen so that half of one data page and half of another another data page are visible at the same time. If I move my finger up or down by a tiny amount (still without letting go), the data pages move by the exact same amount.

To me that's an example of precise drag detection. So you could ask your 265 user to see if they can do that with their watch.

If they can, I'd say it's a bug that onDrag isn't supported. It could be an oversight due to the fact that 255 didn't have a touchscreen, and 265/265s is the first 2x5 generation to have one.

I sent him a message an awaiting an  answer.

Yeah, that's what I did. I doubled check the devices I had selected and only the 265 and 265s had to be removed, hence why I found it weird.