From 215408bb5c2887e8a2cf5ead762e95e000e04c82 Mon Sep 17 00:00:00 2001 From: Raymond Chen Date: Wed, 16 Dec 2015 17:45:56 -0800 Subject: [PATCH] Windows 10 RTM Release - December 2015 Update --- .../MyBackgroundAudioTask.cs | 12 +--- Samples/LockScreenApps/cs/ScenarioInput1.xaml | 34 +++------- .../LockScreenApps/cs/ScenarioInput1.xaml.cs | 63 +------------------ Samples/LockScreenApps/cs/ScenarioList.xaml | 2 +- .../LockScreenApps/cs/ScenarioOutput1.xaml | 5 -- 5 files changed, 14 insertions(+), 102 deletions(-) diff --git a/Samples/BackgroundAudio/cs/BackgroundAudioTask/MyBackgroundAudioTask.cs b/Samples/BackgroundAudio/cs/BackgroundAudioTask/MyBackgroundAudioTask.cs index 484a785114..12cc7634db 100644 --- a/Samples/BackgroundAudio/cs/BackgroundAudioTask/MyBackgroundAudioTask.cs +++ b/Samples/BackgroundAudio/cs/BackgroundAudioTask/MyBackgroundAudioTask.cs @@ -218,7 +218,7 @@ private void UpdateUVCOnNewTrack(MediaPlaybackItem item) /// void smtc_PropertyChanged(SystemMediaTransportControls sender, SystemMediaTransportControlsPropertyChangedEventArgs args) { - // TODO: If soundlevel turns to muted, app can choose to pause the music + // If soundlevel turns to muted, app can choose to pause the music } /// @@ -382,9 +382,6 @@ private void SkipToPrevious() { smtc.PlaybackStatus = MediaPlaybackStatus.Changing; playbackList.MovePrevious(); - - // TODO: Work around playlist bug that doesn't continue playing after a switch; remove later - BackgroundMediaPlayer.Current.Play(); } /// @@ -394,10 +391,6 @@ private void SkipToNext() { smtc.PlaybackStatus = MediaPlaybackStatus.Changing; playbackList.MoveNext(); - - // TODO: Work around playlist bug that doesn't continue playing after a switch; remove later - BackgroundMediaPlayer.Current.Play(); - } #endregion @@ -477,9 +470,6 @@ void BackgroundMediaPlayer_MessageReceivedFromForeground(object sender, MediaPla Debug.WriteLine("Skipping to track " + index); smtc.PlaybackStatus = MediaPlaybackStatus.Changing; playbackList.MoveTo((uint)index); - - // TODO: Work around playlist bug that doesn't continue playing after a switch; remove later - BackgroundMediaPlayer.Current.Play(); return; } diff --git a/Samples/LockScreenApps/cs/ScenarioInput1.xaml b/Samples/LockScreenApps/cs/ScenarioInput1.xaml index 2f29faf1d0..23059165e1 100644 --- a/Samples/LockScreenApps/cs/ScenarioInput1.xaml +++ b/Samples/LockScreenApps/cs/ScenarioInput1.xaml @@ -16,40 +16,26 @@ - In this scenario, the app will request to be added to the lock screen, remove itself from the lock screen, and - query its current lock screen status. + In this scenario, the app will request that the user add it to the lock screen. - Lock screen apps are apps that can notify users when the users are not using their device. Lock screen apps are - special in that they have permission to run in the background. For example, lock screen apps can run code - periodically on a timer every 15 minutes, maintain a TCP socket in the background, or receive push notifications - from the Windows Push Notification Service (WNS). Lock screen apps have the ability to show updates to the user + Lock screen apps are apps that can notify users when the users are not using their device. + Lock screen apps have the ability to show updates to the user on the lock screen by updating badge counts and glyphs, showing toast notifications, or by allowing a text-only - version of their Start tile to appear on the lock screen. An app must be granted permission by the user to be a - lock screen app. + version of their Start tile to appear on the lock screen. - There are only 7 lock screen slots and an app may request to fill a single one of these. Of these seven apps, one - may also take the detailed status slot on the lock screen. If the user declines to give your app permission, you - may not prompt again. Apps can query the current state of the setting and may prompt the user a single time to see - if they want to allow the app to appear on their lock screen. Subsequent attempts to prompt the user will result - in returning the app's current status, without showing any UI to the user. - - - An app must set the appropriate information in the manifest in order to be background capable. In the Visual Studio + An app must set the appropriate information in the manifest in order to appear on the lock screen. In the Visual Studio manifest editor, under the Lock screen notifications option in the Application UI tab, set the value to either "Badge" or "Badge and Tile Text". Additionally, apps must specify a background task of type "Control channel", "Timer", or "Push notification" in the Declarations tab. For more information, see the "Background Tasks" sample. - Users can manually add the app to the lock screen (or remove it) through the Personalize page in PC Settings, or - in the Permissions tab in the app's Settings page. When declared in the manifest as described above, the app will - appear in the list of allowable lock screen apps on the Lock screen tab of the Personalize page. + To appear on the lock screen, the user must add it manually + through the Notifications page in Settings. + When declared in the manifest as described above, the app will + appear in the list of allowable lock screen apps. - -