Talk:How to handle phone calls and other interruptions in Windows Phone
Influencer - Interesting
you show an interesting aspect I haven't known about yet.
Nevertheless I have some comments:
- You got a typo in the title, it has to be 'other' instead of 'others'. As this is not a simple edit but a move I didn't fix that.
- Maybe an explanation why this especially important with 'timer, storyboard, game and FM radio ' apps could help. Perhaps other kinds of apps that are otherwise 'active' are affected, too. I guess it has something to do with actions that are running and should be paused when the call occurs.
- I don't think the Summary is a summary at all. If the aspect of battery savings is important please explain why. That could be a new section then. The Summary should give the short version of the article's content and maybe a conclusion.
01:09, 10 June 2013 (EEST)
Pavan.pareta - Thanks!
Thanks for amendment and comments.
The explanation specially important with 'timer, storyboard, game and FM radio' these are the commonly used in applications and these objects consume the CPU and Battery uses. If your application has a static page such as your application shown any information with some static data, there is NO way or NOT make any sense to handle such kind of scenario on the static data based application or pages in your application.
Let's consider an example: Suppose you have a stopwatch in your application and you are running this app to counting some task, in between you may get a phone call that time your stopwatch should run ?? Answer is NO, you can only handle stopwatch timer through your application by using Stop() method of timer object, in that case OS will not taking care to pause it.
However this article only recommends not forcing to use in every application, it is based on your requirement and; how your application behavior when a phone call arrival...
Pavan Pareta 10:29, 10 June 2013 (EEST)
Hamishwillee - Thomas understands that
Thomas understand why battery and CPU are important - his comment is that "this article does not explain why they are important" not "explain to me". In other words, the comments you just made above belong in the article summary :-)
I note that this states that works on WP8 (ie has the category), but this does not match with ArticleMetadata. Can you do final steps to fully migrate, as discussed here: How_to_capture_screen_programmatically_in_Windows_Phone_7#Hamishwillee_-_What_was_this_tested_on. Specifically update the metadata for page to also include what you tested on and built against - presumably some new WP8 devices and SDK.
If there are differences with WP8 SDK then you can probably update to that too - most people who are active developers will be moving to the new toolchain.
05:12, 11 June 2013 (EEST)
Hamishwillee - Subedited/Reviewed
I've subedited this for English. The most serious change was the Summary - you shouldn't use the summary to explain something new like why you would bother using this code - that should be in your introduction or elsewhere. In any case, the instructions didn't really make much sense because handling the events will be completely app specific - and has much more do do with whether the app is useable than CPU/battery behaviour on Windows Phone. In the case of a stopwatch for example, I would expect it to continue in the event of a notification.
Does microsoft give any advice (LINK) on how to handle the obscure event (ie when to pause and when to ignore?)
Thanks for this!
07:46, 13 June 2013 (EEST)