Xencelabs Pen Displays are supported in the locally terminated mode, where peripheral data is processed locally at the Software Client. It is also supported in the bridged mode, where peripheral data is sent to the desktop for processing.
Support is available when a connection is initiated from a Windows Client to a Windows Graphics or Standard agent.
The following table contains a brief description of the header files included in the Anyware Client SDK for Windows:
Note: Location of the Header Files
The header files are available at the following locations in the Anyware Client SDK for Windows package:
External Dependencies
Boost and Qt are external dependencies that the SDK expects to be installed on the system on which the example code is being built.
The Session Client SDK for Windows supports Wacom tablets in two configurations: bridged, where peripheral data is sent to the desktop for processing, and locally terminated, where peripheral data is processed locally at the Software Client.
The SDK package comes with a sample command line pre-session client called the Collaboration Broker Client Example, which calls the included broker client libraries and enables you to join a PCoIP collaboration session. The Collaboration Broker Client API Example demonstrates the success path for joining a PCoIP collaboration session.
The SDK package comes with a sample command line pre-session client called the Broker Client example, which calls the included broker client libraries and establishes a PCoIP connection. The Broker Client API example demonstrates the success path for establishing new PCoIP sessions.
Do not Use the Broker Client Example in Production
Once you have created the branding package, it can be used by the session client. The pre-session client is responsible for verifying the package and passing it to the session client executable.
To use the branding package: