About Release 1.0.1
Release 1.0.1 is a service release that addresses several issues and improves performance. As always, check the Documentation
tab for instructions on how to get started. If you don't have the Windows Phone SDK yet, grab it here
: There is a breaking change in this release.
As noted below, the WorldCalculationMode property of ARItem has been replaced by a user-definable function. ARItem is now automatically wired up with a function that performs the same work as previously setting WorldCalculationMode to GeoRelativeToLocation. For most existing projects, simply removing the line of code that set WorldCalculationMode will allow your project to compile and run as before.
Below is the changelog for release 1.0.1:
Updated ARHelper.DistanceBetween to use changes suggested by Kenny Spade. The new code is much more accurate and maintainable and fixes issue 8759
where some points were being drawn on the wrong side of the user.
Removed WorldCalculationMode enumeration and WorldCalculationMode property from ARItem. The enumeration was replaced by the property ARItem.WorldCalculation, which can point at any function that will calculate and update an ARItem.
Added two methods to ARHelper that can be used with the ARItem.WorldCalculation property mentioned above. WorldFromGeoLocation and WorldFromRelativeLocation provide the functionality that was previously provided by the WorldCalculationMode enumeration.
Defaulted ARItem.WorldCalculation to point at ARHelper.WorldFromGeoLocation. This means that ARItems will be projected into WorldView using their GeoLocation property by default.
Added code to ARHelper.DistanceBetween to calculate the difference between two points in altitude. If both coordinates have valid altitudes, the difference will be calculated. Otherwise, the difference in altitude will be returned as zero. This will place items on the horizon whenever the altitude of the user or the item is unknown. This change resolves issue 8760
HeadingIndicator did not scale and has been updated to use grid layout. Keep in mind that this control must still have a square aspect ratio for it to be drawn correctly.
OverheadMap_LayoutUpdated was being called very frequently and we were assigning a new clip on every call. We now check to see if the size has actually changed before creating a new geometry and updating the clip.
Removed event handlers from the map control that were attempting to disable panning but were not working.
Updated BingAR and SimpleAR samples to use Grid layout at the root instead of Canvas layout.