Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
Graphics
Input Events Library Reference
The Input Events library provides the framework necessary for Screen Graphics Subsystem to communicate with your touch driver.
Writing a Touch Driver
In order for Screen to be able to detect events from your touch controller, you need to provide a driver for your touch controller.
Communicate with the hardware
A separate thread is used to communicate directly with the hardware via the hardware interface (e.g., I2C, SPI, USB, etc.).

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
- Graphics
  - Gestures Library Reference
    The Gestures library provides gesture recognizers to detect gestures through touch events that occur when you place one or more fingers on a touch screen.
  - Image Library Reference
  - Input Events Library Reference
    The Input Events library provides the framework necessary for Screen Graphics Subsystem to communicate with your touch driver.
    - Writing a Touch Driver
      In order for Screen to be able to detect events from your touch controller, you need to provide a driver for your touch controller.
      - Provide the callback functions
        A set of functions need to be implemented by your touch driver. These callback functions are called into by the Input Events library to fetch the data required to transform the device (touch controller) data into mtouch events.
      - Connect to the Input Events library
        Callback functions and capabilities of your touch controller need to be configured and specified, respectively, before connecting to the Input Events library.
      - Provide initialization and cleanup callback functions
        Screen makes two function calls in the driver: one for initialization and one for cleanup.
      - Communicate with the hardware
        A separate thread is used to communicate directly with the hardware via the hardware interface (e.g., I2C, SPI, USB, etc.).
      - Disconnect from the Input Events library
        In addition to any device cleanup, you need to disconnect from the Input Events library so that any resources allocated by the framework to support your driver are released.
    - Input Events Library Overview
  - OpenWF Configuration Developer's Guide
    If you are integrating a new display, you must configure and provide the parameters of your display based on its specifications via the OpenWF Display Configuration API (Wfdcfg Library).
  - OpenWF Display Server User's Guide
    The OpenWF Display Server (wfd-server) is a resource manager that provides applications the ability to show image buffers directly to the display controller via the OpenWF Display API.
  - Screen Graphics Subsystem Developer's Guide
    QNX Screen Graphics Subsystem is a graphics framework that provides all the functionality necessary to develop interactive user experiences.
  - Video Capture Developer's Guide
    The video capture framework provides applications the ability to capture frames from a video input source. These frames can be passed to a graphics component such as Screen for display.
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX OS in the Amazon cloud environment.
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Communicate with the hardware

QNX SDP8.0Input Events Library ReferenceAPIDeveloperProgramming

A separate thread is used to communicate directly with the hardware via the hardware interface (e.g., I2C, SPI, USB, etc.).

You need to create a separate thread as part of your implementation of the mtouch_driver_init() callback function. Refer to pthread_create() in the QNX OS C Library Reference for more details.

The routine you provide as the argument to pthread_create() needs to retrieve coordinate information from the hardware and then call mtouch_driver_process_packet() to trigger the start or processing the data for the touch-related event.

Page updated: March 05, 2025