Acknowledged

MapView and MapTrackView question

Hi

I want to ask a couple of questions about the behavior of MapView and MapTrackView.

I've searched the topics on the forum and there are some things written about MapView already, but none of them actually solves my issues.

1) setScreenVisible area doesn't seem to be working at all.

No matter what screen coordinates I specify it always shows up full screen both on the simulator and the real device (Oregon 700)

2) I want to handle key and touchscreen events in my own delegate class that inherits Ui.InputDelegate and does what it has to in the onKey() and onTap() functions.

It works all right in the simulator, but on the real device (Oregon 700) it behaves as if these events get handled by the underlying map application and hence never reach my code.

For example my intention is to use the tap screen event to have my own zoom control through the setMapVisibleArea function, that allows the application to "remember" the last used zoom level of the view and use it again when showing it the next time. Very simple to have a variable inside the view class with the current zoom level and change it by tapping the upper half or lower half of the map accordingly. This zoom level variable is afterwards used by setMapVisibleArea to determine the portion of the map shown around the current location.

As I've said, works in the simulator, but not on the device - there tapping on the screen puts the map directly into Preview mode by displaying an Info box with details about what's there on the map under the location the user has tapped etc. and the tap event never reaches the delegate class. This seems to be the default behavior of the map application on Oregon 700 and I haven't found a way to suppress it going to Preview mode.

The map behaves in a slightly different way when displayed in an activity. Then there's a dedicated button on the map's upper left corner (a dot with up, down, left, right arrows around it) which has to be pressed in order to put the map in Preview mode. It will not do it all by itself when just tapping somewhere on the screen. However that's the case only in an activity and not if one just launches the map application standalone (e.g. in classic mode) or when using the MapView and MapTrackView classes

I hope someone will be able to give me some tips and advice.

Thanks

Nick

  • Hi Coleman

    I just wanted to check whether there's a positive outcome regarding this issue with the MapTrackView usage on Oregon devices.

    Will there be any changes included in the next firmware update for Oregon when it is released?

    Best regards,

    Nick

  • Nick, As per our email conversation, I've got this working with some of our engineers and we are trying to decide if this is device side or if we are doing something wrong in our simulator. I've also moved this to our bug reports section to better communicate the status so we don't get lost in threads. Thanks!
  • Hi Not sure about the way and the typical timeframe the work on investigating bug reports is scheduled, but will you please drop a word here to tell me whether that'll get fixed in some future firmware update for the Oregon 700/750 devices. Thank you,  Nick
  • I've sent code samples demonstrating the problem. Thank you for looking into it. IMHO if the default behavior of the map application on Oregon devices is changed to be the same like when the map app is invoked from an Activity (i.e. with a dedicated button to enable map panning) the issues will get solved as the map will not handle the clicking and swiping events unless the user deliberately swithes the panning mode on. 
  • [quote userid="113766" url="~/developer/connect-iq/f/discussion/168369/mapview-and-maptrackview-question/911229"]To repeat again - the bahavior in the simulator is OK, it's the real device that fails.[/quote] For MapView and MapTrackView in general, the sim doesn't always show what happens on a real device and I go by the real devices.  And there are differences between watches, Edge devices and the Oregon/Rino.