2.4.30 MSOPATHTYPE
The MSOPATHTYPE enumeration, as shown in the following table, specifies how the individual pieces of a path SHOULD be interpreted.
Name |
Value |
Meaning |
---|---|---|
0x00000000 |
For each POINT record, as defined in section 2.2.55, in the array, add a straight line segment from the current ending POINT to the new POINT. The number of POINT values to process equals the number of segments. The last POINT in the array becomes the new ending POINT. |
|
0x00000001 |
For each segment, three POINT values are used to draw a cubic Bezier curve. The first two POINT values are control POINT values, and the last POINT is the new ending POINT. The number of POINT values consumed is three times the number of segments. |
|
0x00000002 |
Start a new sub-path by using a single POINT. The starting POINT becomes the current ending POINT. The value of the segment field MUST be zero. The number of POINT values used is one. |
|
0x00000003 |
If the starting POINT and the ending POINT are not the same, a single straight line is drawn to connect the starting POINT and the ending POINT of the path. The number of segments MUST be one. The number of POINT values used is zero. |
|
0x00000004 |
The end of the current path. All consecutive lines and fill values MUST be drawn before any subsequent path or line is drawn. The number of segments MUST be zero. The number of POINT values used is zero. |
|
0x00000005 |
The MSOPATHINFO record, as defined in section 2.2.53, is treated as an MSOPATHESCAPEINFO record, as defined in section 2.2.54. |
|
0x00000006 |
The MSOPATHINFO record is treated as an MSOPATHESCAPEINFO record specific to the client. |