Tapped Routed Event Args. Get Position(UIElement) Method
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
public: virtual Point GetPosition(UIElement ^ relativeTo) = GetPosition;
Point GetPosition(UIElement const& relativeTo);
public Point GetPosition(UIElement relativeTo);
Public Function GetPosition (relativeTo As UIElement) As Point
Any UIElement-derived object that is connected to the same object tree. To specify the object relative to the overall coordinate system, use a relativeTo value of null.
A Point that represents the current x- and y-coordinates of the mouse pointer position. If null was passed as relativeTo, this coordinate is for the overall window. If a relativeTo value other than null was passed, this coordinate is relative to the object referenced by relativeTo.
Windows 8 behavior
Windows 8 had an issue with the data for the RightTapped event, where the X and Y values for the point you'd get from RightTappedRoutedEventArgs.GetPosition were reversed (X was really Y; Y was really X). This issue has been fixed starting with Windows 8.1. But if you're retargeting a Windows 8 app for Windows 8.1, you might have had code that worked around this issue by swapping the X and Y back. If so, remove that code when you retarget because the issue is now fixed.
Apps that were compiled for Windows 8 but running on Windows 8.1 continue to use the Windows 8 behavior.