StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12735796
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-10-04T20:57:10.037
FavoriteCount
0
LastActivityDate
2012-10-04T20:57:10.037
LastEditDate
LastEditorUserId
0
OwnerUserId
890018
ParentId
12694915
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Instead of Resizing existing content it may be easier to have a separate set of content that is hidden until the user moves to snapped mode. Use the VisualStateGroups to hide/show the appropriate set of content for the given full-screen/snapped view. So instead of resizing existing fields: <pre><code><Page> <Grid> <Grid x:Name="FullScreenLayout">... </Grid> <Grid x:Name="SnappedScreenLayout">... </Grid> <VisualStateManager.VisualStateGroups>  <VisualStateGroup x:Name="ApplicationViewStates"> <VisualState x:Name="Snapped"> <Storyboard> <ObjectAnimationUsingKeyFrames Storyboard.TargetName="FullScreenLayout" Storyboard.TargetProperty="Visibility"> <DiscreteObjectKeyFrame KeyTime="0" Value="Collapsed"/> </ObjectAnimationUsingKeyFrames> <ObjectAnimationUsingKeyFrames Storyboard.TargetName="SnappedScreenLayout" Storyboard.TargetProperty="Visibility"> <DiscreteObjectKeyFrame KeyTime="0" Value="Visible"/> </ObjectAnimationUsingKeyFrames> </Storyboard> </VisualState> </VisualStateGroup> </VisualStateManager.VisualStateGroups> </Grid> </Page> </code></pre> Here were just hiding the full-screen layout when we're in snapped mode and displaying our snapped mode layout. There is more Xaml but it's contained and allows you to provide a view-specific layout, which makes the Xaml cleaner and easier to read.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POScreen Goes Black in Metro Apps
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFaster Solutions
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POScreen Goes Black in Metro Apps
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COI get your point, but don't you think there should be some other solution to this? I mean I have to develop a complete UI seperately for Snap View..
 singulars
 PostPostId
 PO
 UserUserId
 USuser1714962
2. COI think this is what MS expect you to do and the project templates create a separate, hidden, ListView that is only shown in Snapped View. Most apps will have completely different functionality and layouy in Snapped view (mine do). This was the feedback I had from MS when participating in their early adopter sessions.
 singulars
 PostPostId
 PO
 UserUserId
 USFaster Solutions

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.