StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19946155
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-13T05:39:26.717
FavoriteCount
0
LastActivityDate
2013-11-14T17:34:18.963
LastEditDate
2013-11-14T17:34:18.963
LastEditorUserId
1938624
OwnerUserId
1938624
ParentId
19641199
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I figured out how to do it. I am a C++ newbie so there may be much better ways to do this, but my way works. (FYI - I wrote an article about this on Nokia's Developer site: <a href="http://developer.nokia.com/Community/Wiki/Multi-touch_handling_using_DirectX_C%2B%2B#PointerPoint" rel="nofollow">http://developer.nokia.com/Community/Wiki/Multi-touch_handling_using_DirectX_C%2B%2B#PointerPoint</a> ) You need to keep track of the PointerId inside of the PointerPoint. I store the PointerId in the OnPointerPressed event in a std::unordered_map. The key (unsigned int) is the PointerId. You then erase them from the map when you get the OnPointerReleased event. The PointerId will match up. It turns out that for every new finger, you get a new PointerId... even if you release your first finger and put it back down again. Then, when you get to your OnPointerMoved event handler, you just have to call the size() function on your unordered_map to find out how many touches you currently have on screen. The reason I'm using the unordered_map is because I needed to keep track of previous point positions. I realize that you can probably get old positions using the GetIntermediatePoints method, but I didn't want to have to troubleshoot something new... Anyways, hope this helps. Code below: EDIT: Code updated to handle the x move events you get from each touch for each frame. Like I said, this isn't the best, but it works. <pre><code>#include <unordered_map> std::unordered_map<unsigned int, Windows::UI::Input::PointerPoint^> m_pointerIds; std::unordered_map<unsigned int, Windows::UI::Input::PointerPoint^> m_oldPoints; void Direct3DBackground::OnPointerPressed(DrawingSurfaceManipulationHost^ sender, PointerEventArgs^ args) { m_pointerIds.emplace(args->CurrentPoint->PointerId, args->CurrentPoint); m_oldPoints.emplace(args->CurrentPoint->PointerId, args->CurrentPoint); } void Direct3DBackground::OnPointerMoved(DrawingSurfaceManipulationHost^ sender, PointerEventArgs^ args) { if (m_pointerIds.size() == 1) { DoSomethingForOneTouch(args); } else if (m_pointerIds.size() == 2) { UINT changedPointId = args->CurrentPoint->PointerId; UINT frameId = args->CurrentPoint->FrameId; UINT otherPointId; for (auto it = m_pointerIds.begin(); it != m_pointerIds.end(); ++it) { if (it->first != changedPointId) { otherPointId = it->first; break; } } m_oldPoints[changedPointId] = m_pointerIds[changedPointId]; m_pointerIds[changedPointId] = args->CurrentPoint; if (m_pointerIds[otherPointId]->FrameId == frameId) { //DO YOUR CALCULATION using new points and old points //as both touches have been updated for the current frame. } } } void Direct3DBackground::OnPointerReleased(DrawingSurfaceManipulationHost^ sender, PointerEventArgs^ args) { m_pointerIds.erase(args->CurrentPoint->PointerId); m_oldPoints.erase(args->CurrentPoint->PointerId); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to handle multi touch in windows phone 8 app
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLee McPherson
UserOwnerUserId
1. USLee McPherson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.