You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/atl/atl-collection-classes.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ For a list of the CTraits classes, see [Collection Classes](../atl/collection-cl
97
97
98
98
The following diagram shows the class hierarchy for the CTraits classes.
99
99
100
-
![Traits hierarchy for collection classes](../atl/media/vctraitscollectionclasseshierarchy.gif"Traits hierarchy for collection classes")
100
+
![Diagram that shows the traits hierarchy for collection classes.](../atl/media/vctraitscollectionclasseshierarchy.gif"Traits hierarchy for collection classes")
A connectable object is one that supports outgoing interfaces. An outgoing interface allows the object to communicate with a client. For each outgoing interface, the connectable object exposes a connection point. Each outgoing interface is implemented by a client on an object called a sink.
![Diagram that shows the connection points on a client object and a connectable object.](../atl/media/vc2zw31.gif"Connection points")
13
13
14
14
Each connection point supports the [IConnectionPoint](/windows/win32/api/ocidl/nn-ocidl-iconnectionpoint) interface. The connectable object exposes its connection points to the client through the [IConnectionPointContainer](/windows/win32/api/ocidl/nn-ocidl-iconnectionpointcontainer) interface.
Copy file name to clipboardExpand all lines: docs/atl/example-implementing-a-property-page.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Click **OK** to have the wizard generate your property page.
60
60
61
61
Now that your property page has been generated, you'll need to add a few controls to the dialog resource representing your page. Add an edit box, a static text control, and a check box and set their IDs as shown below:
62
62
63
-
![Editing a dialog resource](../atl/media/ppgresourcelabeled.gif"Editing a dialog resource")
63
+
![Screenshot of a dialog resource in the visual editor.](../atl/media/ppgresourcelabeled.gif"Editing a dialog resource")
64
64
65
65
These controls will be used to display the file name of the document and its read-only status.
![Diagram of the classes and interfaces used to define an A T L object.](../atl/media/vc307y1.gif"ATL structure")
13
13
14
14
> [!NOTE]
15
15
> This diagram shows that `CComObject` is derived from `CYourClass` whereas `CComAggObject` and `CComPolyObject` include `CYourClass` as a member variable.
Copy file name to clipboardExpand all lines: docs/atl/identifying-the-elements-of-the-dhtml-control-project.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ A DHTML control is similar to any ATL control, except:
19
19
20
20
The following graphic illustrates the relationship between your DLL, the DHTML control, the Web browser, and the HTML resource.
21
21
22
-
![Elements of a DHTML control project](../atl/media/vc52en1.gif"Elements of a DHTML control project")
22
+
![Diagram of the elements of a DHTML control project.](../atl/media/vc52en1.gif"Elements of a DHTML control project")
23
23
24
24
> [!NOTE]
25
25
> The names on this graphic are placeholders. The names of your HTML resource and the interfaces exposed on your control are based on the names you assign them in the ATL Control Wizard.
@@ -40,7 +40,7 @@ In this graphic, the elements are:
40
40
41
41
The ATL Control Wizard generates a control with default code in both the HTML resource and the .cpp file. You can compile and run the control as generated by the wizard, and then view the control in either the Web browser or the ActiveX Control Test Container. The picture below shows the default ATL DHTML control with three buttons displayed in Test Container:
See [Creating an ATL DHTML Control](../atl/creating-an-atl-dhtml-control.md) to get started building a DHTML control. See [Testing Properties and Events with Test Container](../mfc/testing-properties-and-events-with-test-container.md) for information on how to access Test Container.
Copy file name to clipboardExpand all lines: docs/build-insights/tutorials/vcperf-and-wpa.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ NOTE: Windows 8 or above is required for installing the Windows Performance Anal
31
31
32
32
1. When prompted for the features that you want to install, select the **Windows Performance Toolkit**. You may select other features if you wish, but they're not required to install WPA.
33
33
34
-
34
+
35
35
36
36
### <aname="configuration-steps"></a> To configure WPA
37
37
@@ -75,7 +75,7 @@ To view C++ Build Insights data, first collect it into a trace file by following
75
75
76
76
Here's what a typical *vcperf.exe* command sequence looks like in a developer command prompt window:
79
79
80
80
### Important notes about vcperf.exe
81
81
@@ -104,7 +104,7 @@ Launch WPA and open the trace you just collected. WPA should recognize it as a C
104
104
105
105
If you can't see these views, double-check that WPA is configured correctly, as described in [Step 1](#configuration-steps). You can view your build data by dragging the views into the empty Analysis window on the right, as shown here:
106
106
107
-
107
+
108
108
109
109
Other views are available in the Graph Explorer panel. Drag them into the Analysis window when you're interested in the information they contain. A useful one is the CPU (Sampled) view, which shows CPU utilization throughout your build.
![Diagram that shows the stack frame layout for functions.](media/arm64-exception-handling-stack-frame.png"stack frame layout")
51
51
52
52
For frame chained functions, the fp and lr pair can be saved at any position in the local variable area, depending on optimization considerations. The goal is to maximize the number of locals that can be reached by a single instruction based on the frame pointer (x29) or stack pointer (sp). However, for `alloca` functions, it must be chained, and x29 must point to the bottom of stack. To allow for better register-pair-addressing-mode coverage, nonvolatile register save areas are positioned at the top of the Local area stack. Here are examples that illustrate several of the most efficient prolog sequences. For the sake of clarity and better cache locality, the order of storing callee-saved registers in all canonical prologs is in "growing up" order. `#framesz` below represents the size of entire stack (excluding alloca area). `#localsz` and `#outsz` denote local area size (including the save area for the \<x29, lr> pair) and outgoing parameter size, respectively.
53
53
@@ -182,7 +182,7 @@ The .pdata records are an ordered array of fixed-length items that describe ever
182
182
183
183
Each .pdata record for ARM64 is 8 bytes in length. The general format of each record places the 32-bit RVA of the function start in the first word, followed by a second word that contains either a pointer to a variable-length .xdata block, or a packed word describing a canonical function unwinding sequence.
184
184
185
-
185
+
186
186
187
187
The fields are as follows:
188
188
@@ -198,7 +198,7 @@ The fields are as follows:
198
198
199
199
When the packed unwind format is insufficient to describe the unwinding of a function, a variable-length .xdata record must be created. The address of this record is stored in the second word of the .pdata record. The format of the .xdata is a packed variable-length set of words:
200
200
201
-
201
+
202
202
203
203
This data is broken into four sections:
204
204
@@ -330,7 +330,7 @@ For functions whose prologs and epilogs follow the canonical form described belo
330
330
331
331
The format of a .pdata record with packed unwind data looks like this:
332
332
333
-
![.pdata record with packed unwind data](media/arm64-exception-handling-packed-unwind-data.png".pdata record with packed unwind data")
333
+
![.pdata record with packed unwind data.](media/arm64-exception-handling-packed-unwind-data.png".pdata record with packed unwind data")
Copy file name to clipboardExpand all lines: docs/build/clang-support-cmake.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ You can use Visual Studio with Clang to edit and debug C++ CMake projects that t
25
25
26
26
For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang compiler for Windows** under **Desktop development with C++** optional components. When using a custom Clang installation, check the **C++ Clang-cl for v142 build tools** component.
1. To make modifications to this configuration, use the **CMake Settings Editor**. For more information, see [Customize CMake build settings in Visual Studio](customize-cmake-settings.md).
45
45
@@ -76,6 +76,6 @@ After you have set up a Clang configuration, you can build and debug the project
76
76
77
77
When debugging, you can use breakpoints, memory and data visualization, and most other debugging features. Some compiler-dependent features such as Edit and Continue are not available for Clang configurations.
0 commit comments