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 2 years ago

    Also don't forget, that whether you see those +/- buttons on F7/EPIX when entering the map screen depends on state of map screen shown on device previously, doesn't matter whether in your CIQ app or native activity app. And you can try to force MAP_MODE_PREVIEW as you want. 

    All in all, this is great example where it would be enough, if some person from CIQ team spend one day trying to implement the screen to some meaningful app and fix all issues/glitches he found in the process instead of waiting for us to to report them without getting any feedback. This should happened years ago after 3.0 release, where maps was one of the biggest addition. This is exactly what I tought by bullet #1 in this post: https://forums.garmin.com/developer/connect-iq/f/discussion/7985/general-wishes-ideas-for-connect-iq-future/1368779#1368779 

    On the other hand, I think behaviour of map screen on these new devices with both touch/buttons controls make sense. So its only on CIQ platform to incorporate changes to be compatible with this approach - like disabling movement of the map when sliding to different screen from map on preview mode (just like it is on native activity apps). 


Comment
  • over 2 years ago

    Also don't forget, that whether you see those +/- buttons on F7/EPIX when entering the map screen depends on state of map screen shown on device previously, doesn't matter whether in your CIQ app or native activity app. And you can try to force MAP_MODE_PREVIEW as you want. 

    All in all, this is great example where it would be enough, if some person from CIQ team spend one day trying to implement the screen to some meaningful app and fix all issues/glitches he found in the process instead of waiting for us to to report them without getting any feedback. This should happened years ago after 3.0 release, where maps was one of the biggest addition. This is exactly what I tought by bullet #1 in this post: https://forums.garmin.com/developer/connect-iq/f/discussion/7985/general-wishes-ideas-for-connect-iq-future/1368779#1368779 

    On the other hand, I think behaviour of map screen on these new devices with both touch/buttons controls make sense. So its only on CIQ platform to incorporate changes to be compatible with this approach - like disabling movement of the map when sliding to different screen from map on preview mode (just like it is on native activity apps). 


Children
No Data