|
16 | 16 |
|
17 | 17 | <StackPanel>
|
18 | 18 | <TextBlock Style="{StaticResource DescriptionTextStyle}" TextWrapping="Wrap">
|
19 |
| - In this scenario, the app will request to be added to the lock screen, remove itself from the lock screen, and |
20 |
| - query its current lock screen status. |
| 19 | + In this scenario, the app will request that the user add it to the lock screen. |
21 | 20 | <LineBreak/>
|
22 | 21 | <LineBreak/>
|
23 |
| - Lock screen apps are apps that can notify users when the users are not using their device. Lock screen apps are |
24 |
| - special in that they have permission to run in the background. For example, lock screen apps can run code |
25 |
| - periodically on a timer every 15 minutes, maintain a TCP socket in the background, or receive push notifications |
26 |
| - from the Windows Push Notification Service (WNS). Lock screen apps have the ability to show updates to the user |
| 22 | + Lock screen apps are apps that can notify users when the users are not using their device. |
| 23 | + Lock screen apps have the ability to show updates to the user |
27 | 24 | on the lock screen by updating badge counts and glyphs, showing toast notifications, or by allowing a text-only
|
28 |
| - version of their Start tile to appear on the lock screen. An app must be granted permission by the user to be a |
29 |
| - lock screen app. |
| 25 | + version of their Start tile to appear on the lock screen. |
30 | 26 | <LineBreak/>
|
31 | 27 | <LineBreak/>
|
32 |
| - There are only 7 lock screen slots and an app may request to fill a single one of these. Of these seven apps, one |
33 |
| - may also take the detailed status slot on the lock screen. If the user declines to give your app permission, you |
34 |
| - may not prompt again. Apps can query the current state of the setting and may prompt the user a single time to see |
35 |
| - if they want to allow the app to appear on their lock screen. Subsequent attempts to prompt the user will result |
36 |
| - in returning the app's current status, without showing any UI to the user. |
37 |
| - <LineBreak/> |
38 |
| - <LineBreak/> |
39 |
| - An app must set the appropriate information in the manifest in order to be background capable. In the Visual Studio |
| 28 | + An app must set the appropriate information in the manifest in order to appear on the lock screen. In the Visual Studio |
40 | 29 | manifest editor, under the Lock screen notifications option in the Application UI tab, set the value to either
|
41 | 30 | "Badge" or "Badge and Tile Text". Additionally, apps must specify a background task of type "Control channel",
|
42 | 31 | "Timer", or "Push notification" in the Declarations tab. For more information, see the "Background Tasks" sample.
|
43 | 32 | <LineBreak/>
|
44 | 33 | <LineBreak/>
|
45 |
| - Users can manually add the app to the lock screen (or remove it) through the Personalize page in PC Settings, or |
46 |
| - in the Permissions tab in the app's Settings page. When declared in the manifest as described above, the app will |
47 |
| - appear in the list of allowable lock screen apps on the Lock screen tab of the Personalize page. |
| 34 | + To appear on the lock screen, the user must add it manually |
| 35 | + through the Notifications page in Settings. |
| 36 | + When declared in the manifest as described above, the app will |
| 37 | + appear in the list of allowable lock screen apps. |
48 | 38 | </TextBlock>
|
49 |
| - <StackPanel Orientation="Horizontal" > |
50 |
| - <Button x:Name="RequestLockScreenAccess" Content="Request lock screen access"/> |
51 |
| - <Button x:Name="RemoveLockScreenAccess" Content="Remove lock screen access"/> |
52 |
| - <Button x:Name="QueryLockScreenAccess" Content="Query lock screen access"/> |
53 |
| - </StackPanel> |
| 39 | + <Button Content="Go to Notification Settings" Click="{x:Bind OpenNotificationSettings}" Margin="0,10,0,0"/> |
54 | 40 | </StackPanel>
|
55 | 41 | </Page>
|
0 commit comments