PagesPerSheetDirection Enumeration
Assembly: ReachFramework (in reachframework.dll)
| Member name | Description | |
|---|---|---|
| BottomLeft | Pages appear in columns, from top to bottom and right to left relative to page orientation. | |
| BottomRight | Pages appear in columns, from top to bottom and left to right relative to page orientation. | |
| LeftBottom | Pages appear in rows, from right to left and top to bottom relative to page orientation. | |
| LeftTop | Pages appear in rows, from right to left and bottom to top relative to page orientation. | |
| RightBottom | Pages appear in rows, from left to right and top to bottom relative to page orientation. | |
| RightTop | Pages appear in rows, from left to right and bottom to top relative to page orientation. | |
| TopLeft | Pages appear in columns, from bottom to top and right to left relative to page orientation. | |
| TopRight | Pages appear in columns, from bottom to top and left to right relative to page orientation. | |
| Unknown | The feature (whose options are represented by this enumeration) is set to an option not defined in the Print Schema. |
Use the values of this type primarily for these purposes:
-
As members of the PagesPerSheetDirectionCapability collection, which is a property of PrintCapabilities, these values indicate the page arrangements that the printer supports.
-
As the value of the PagesPerSheetDirection property of a PrintTicket, the value directs the printer to arrange pages of content in a specified direction.
The Unknown value is never used in properties of PrintCapabilities objects.
You should never set a PrintTicket property to Unknown. If some other PrintTicket producing application has created a PrintTicket document that sets the pages-per-sheet-direction feature to an unrecognized option (that is, an option that is not defined in the Print Schema), then a PrintTicket object in your application that is constructed with that document will have Unknown as the value of the PagesPerSheetDirection property.
Although the PrintTicket and PrintCapabilities classes cannot be inherited, you can extend the Print Schema to recognize print device features that are not accounted for in the PrintTicket or PrintCapabilities classes. For more information see How to: Extend the Print Schema and Create New Print System Classes.
The following example shows how to test a printer's capabilities and configure the print job to take advantage of them. For the complete example, see Creating an XPS Document Sample.
Windows 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition
The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.