2. Mobile first who is the main ups and downs----a common program

If there is any problem with the direction of movement, please refer to ===> exception handling summary-Mobile series (points)

Create a new generic project

Project Preview

Open Win8.1mainpage, put a button

Open Wp8.1mainpage, put a button

The UI part is certainly not universal, then the general is only the code common, look at the picture

Click the button first to generate an event that will be used

Create a new MainPage class in the General Code section (in fact the name doesn't matter, it can be changed inside)

The picture says it's clear.

Set up something to debug

Debug a little bit of WP8.1

OK,

and debug the Win8.1.

OK,

Add: 4 numbers appear

The Override debug counter has two sets of numbers. The settings that appear in the upper-left corner of the screen apply only to your application. The settings that appear in the upper-right corner apply to the entire system and are also responsible for drawing other applications to the composite desktop. The right counter comes from a composite Microsoft Directcomposition component that typically handles Microsoft Windows. Basically, if you set EnableFramerateCounter to true, Idcompositiondevicedebug is also called in the underlying component :: Enabledebugcounters. The results are counters specific to applications that use XAML and directcomposition counters for all applications that you debug in the Windows store app.

The format of the frame rate counter displayed in the window chrome is:

000	000	...	...	000	000
APP fps	APP CPU	...	...	Sys fps	Sys CPU

• app fps: The application's UI thread frame rate (in frames per second).
• App CPU: The CPU usage (in milliseconds) of the application UI thread per frame.
• Sys fps: system-wide composite engine frame rate in frames per second. This is usually limited to 60.
• Sys CPU: The system-wide overall CPU utilization of the composite thread per frame (in milliseconds).

App fps values are specifically reported on the UI thread. The frequency of refreshes in applications that are associated with a composite thread, but not related to the UI thread, can appear significantly higher. For more information about the things that each thread is responsible for, see performance Best practices for Windows store apps.

OnLaunched is a good place to change the debugsettings value. Another possibility is a App() constructor.

Windows 8 Behavior

In Windows 8, the counters used other formats, and the Directcomposition counters were not merged. The format is:

000	000	000000	000	000	000
Comp fps	UI fps	Memory	Batch	Comp ms	UI ms

• Comp fps: frame rate for composite threads
• UI fps: The frame rate of the UI thread
• Memory : usage of textures
• Batch: count of surfaces sent to the graphics processing Unit (GPU)
• Comp ms: time per frame consumed on a composite thread (in milliseconds)
• UI Ms: The amount of time (in milliseconds) spent per frame on the UI thread

Requirements

Minimum support client	Windows 8
Minimum supported server	Windows Server 2012
Name space	Windows.UI.Xaml Windows::ui::xaml [C + +]
Meta data	Windows.winmd

Reference Link: https://msdn.microsoft.com/zh-cn/zh-cn/windows/apps/windows.ui.xaml.debugsettings.enableframeratecounter

2. Mobile first who is the main ups and downs----a common program