Closed saip closed 5 years ago
Working with @saip we noticed some of the strange behavior I was seeing with D&D in Pro was caused by the lpkx not being package as "schema only" so I will repackage
Once PR #662 is merged into this branch we can resume testing
Verified that all issues except #648 are working as expected with this PR - with #648 we are experiencing a lockup issue on 2.4 daily as reported here: https://github.com/Esri/distance-direction-addin-dotnet/issues/648#issuecomment-499677301
I'm noticing the lockup problem https://github.com/Esri/distance-direction-addin-dotnet/issues/648#issuecomment-499677301 also in the dev branch so I feel confident it is not related to this PR. It is a very strange problem, that seems to require those exact set up steps.
But at this point I think this PR is OK to merge if @saip has no more changes ( just noticed a commit so thought I would double check)
@csmoore No more changes pending from us. Please merge.
This build addresses the GitHub tickets mentioned below:
608 - Distance Unit in Feature Tables is not based on Resource Value - verified
635 - Cannot drag row to bottom in Range Rings Distances table - - verified
639 - Add gradian as an angle unit of measure - verified
647 - Clear and Save As buttons should have a hover action - verified
648 - Using Addin with existing Pro project at a different scale causes "Spatial Index Grid Size" error - verified