2 Answers

• I spent hours try to figure out how to work around this. In the end it was the simple answer that worked the best.

  Add a variable that is visible to the entire section of code used for the MapView.

  var preventRefresh = false;
  

  Then in your code add an event listener for the MapView click event and set the variable to true if the clicksource was 'pin'.

  mapview.addEventListener('click',function(evt)
  {
      var clickSource = evt.clicksource;
  
      if(evt.clicksource == 'pin'){
          preventRefresh = true;
      }
  });
  

  Then in your code for the regionChanged event listener check to make sure the variable is 'false' before firing the code to for the regionChanged event. (I have a function to update my annotations).

  mapview.addEventListener('regionChanged', function(e){
      if(preventRefresh == false){
          refreshAnnotations()
      }
      else{
          preventRefresh = false;
      }
  });
  

  Don't forget to set the else to reset your variable to false.

  Now the regionChanged code is ignored when the pin is clicked causing the bubble above it to make the MapView move.

  I hope this prevents male-pattern-baldness in someone else. For me, it's too late.

• For those that may run into this thread with the same issue: I did end up getting more creative with how I load my annotations.

  I have some logic that loops through annotations, deletes annotations that are now off screen, adds new annotations, and leaves annotations that are still on the screen alone.