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 in reply to Jan Čapek

    On 3.0, you couldn't have the MapView as your first view.  This has been changed in 3.1.  So in 3.0, if you wanted your main view to be a MapView, you first had to have a dummy view that would just push a MapView.  It's nice that they removed this restriction, but could cause issues on 3.0 devices if you don't deal with it properly.  I've chosen to leave in the dummy view that just pushes the MapView.

Comment
  • over 5 years ago in reply to Jan Čapek

    On 3.0, you couldn't have the MapView as your first view.  This has been changed in 3.1.  So in 3.0, if you wanted your main view to be a MapView, you first had to have a dummy view that would just push a MapView.  It's nice that they removed this restriction, but could cause issues on 3.0 devices if you don't deal with it properly.  I've chosen to leave in the dummy view that just pushes the MapView.

Children