Ticket Created
over 5 years ago

WERETECH-7119, WERETECH-7120, WERETECH-8181

Split issues in this thread into multiple issues.

MapView and MapTrackView classes are broken - even more on CIQ3.1

Hi, 

not only that CIQ 3.0 implementation of MapView and MapTrackView still have more issues than actual working features, CIQ 3.1 even made them worse. 

Newly, UI rendered by both classes can not be refreshed on CIQ 3.1 devices by calls from code after first initialisation - for example by setMapVisibleArea method as it is described here:

https://forums.garmin.com/developer/connect-iq/f/discussion/191378/fenix-6-ciq-maps-implementation/932413#932413

I can summary also the older issues if it will help somebody to take care of them in one run. But some of them are already mentioned on various places of the forum without any positive reaction from CIQ team, so I don't want to waste time if nobody ask for them.   

Will there be please finally time to fix those important parts of CIQ after settling down dust from CIQ 3.1 public release? This is kind of things why Connect IQ is extremely hard to use for any more complex apps which should be perfectly doable according to documentation.  In my case I have to disable maps on all CIQ 3.1 devices until the problems will be solved leaving my users confused again. Disappointed

Jan Čapek
Parents
  • over 5 years ago

    There was a major re-write of the UI portion of the CIQ for 3.1, which was the reason we wanted to support native views as base view for the watch app, CIQ 3.1 removes the restriction of having the base view to be generic view and native views can be pushed as base view, because of this major overhaul CIQ 3.1 was a little bumpy. 

    The flicker issue for the map track view, when updating the elements on the map has been addressed in the beta release for Fenix6 fw 4.62. This will be rolled out to other devices soon.

Comment
  • over 5 years ago

    There was a major re-write of the UI portion of the CIQ for 3.1, which was the reason we wanted to support native views as base view for the watch app, CIQ 3.1 removes the restriction of having the base view to be generic view and native views can be pushed as base view, because of this major overhaul CIQ 3.1 was a little bumpy. 

    The flicker issue for the map track view, when updating the elements on the map has been addressed in the beta release for Fenix6 fw 4.62. This will be rolled out to other devices soon.

Children
  • over 5 years ago in reply to Anshul.ConnectIQ

    Thanks for the update.

    I can confirm the F6 with 4.62 does appear to have fixed the flicker problem related to PolyLine's and Markers.  Most of the 3.1 issues have now been resolved for me. 

    The one issue I keep personally running into is the golf maps.  Thankfully in my case, the overlap between those who use my Dog Tracker apps and golf and use an F6 or Marq seems to be fairly small.