QNX SDP 7 (like QNX SDP 6.6) includes the Screen Graphics Subsystem, which replaces the Photon microGUI. You'll need to rewrite your Photon applications if you're migrating from QNX SDP 6.5, or QNX SDP 6.5 SP1 without Screen.
If you're migrating your Screen applications from QNX SDP 6.5 SP1:
Ensure that the background color that's specified in the display section of your configuration file, graphics.conf, is a 24-bit value.
Ensure that you're not using any properties that we discontinued:
| Instead of using: | Use: |
|---|---|
| SCREEN_PROPERTY_ALTERNATE_WINDOW | SCREEN_PROPERTY_ALTERNATE |
| SCREEN_PROPERTY_DEVICE_INDEX | SCREEN_PROPERTY_DEVICE |
| SCREEN_PROPERTY_KEY_FLAGS | SCREEN_PROPERTY_FLAGS |
| SCREEN_PROPERTY_KEY_MODIFIERS | SCREEN_PROPERTY_MODIFIERS |
| SCREEN_PROPERTY_KEY_SCAN | SCREEN_PROPERTY_SCAN |
| SCREEN_PROPERTY_KEY_SYM | SCREEN_PROPERTY_SYM |
| SCREEN_PROPERTY_KEYBOARD_FOCUS | SCREEN_PROPERTY_FOCUS |
The following properties have no replacement:
Ensure that you're not using any properties that we discontinued for an API object:
Ensure that you're not using the screen_tab_focus() function that we discontinued.
Ensure that you're not using any of the following input session modes that we discontinued:
Note that the values of following members of Screen Property Types have changed:
| Member | Was: | Is now: |
|---|---|---|
| SCREEN_PROPERTY_FRONT_BUFFERS | 15 | 171 |
| SCREEN_PROPERTY_MIRROR_MODE | 58 | 150 |
Note that in QNX SDP 7, you no longer configure touch devices (also called mtouch for multitouch devices) as part of Screen's configuration file (graphics.conf).
Instead, you configure the touch devices for your platform using the mtouch.conf and scaling.conf configuration files. These files are included in the BSP (Board Support Package) that are availabe for the QNX Neutrino RTOS. Refer to the appropriate BSP User's Guide for your target hardware.
Note that in QNX SDP 7, Screen no longer loads and starts touch drivers. You must use the mtouch service to start the touch drivers. For more information on the mtouch service, see the Utilities and binaries chapter of Screen Developer's Guide.
If you're migrating your Screen applications from QNX SDP 6.6, follow the guidelines provided above for migrating from QNX SDP 6.5 SP1, and then also do the following:
In QNX SDP 7, Screen locally allocates resources to track the API object when your application calls the corresponding screen_get_*_property_pv() function to retrieve the object.
If you call screen_get_window_property_pv() to retrieve the group (SCREEN_PROPERTY_GROUP) or the stream (SCREEN_PROPERTY_STREAM) objects associated with the window, you must call the appropriate screen_destroy_*() function to free up these resources when you're finished using each of these objects.
If you call screen_get_pixmap_property_pv() to retrieve the group (SCREEN_PROPERTY_GROUP) object associated with the pixmap, you must call screen_destroy_group() to free up these resources when you're finished using the group.
If you call screen_get_session_property_pv() to retrieve the window (SCREEN_PROPERTY_WINDOW) object associated with the session, you must call screen_destroy_window() to free up these resources when you're finished using the window.
Note that in QNX SDP 7, the following properties are affected when a window's SCREEN_PROPERTY_SELF_LAYOUT property is set to 1:
When these layout-related properties are changed, a SCREEN_EVENT_PROPERTY event is sent to notify the window manager (or parent) of the property change.
For more information on Screen, see the Screen Developer's Guide.
In QNX SDP 7, the image libraries are no longer statically linked to the image codecs. You need to put the libraries that the codecs depend on, in addition to any required image codecs and the image configuration file, onto targets running your application.
The following is a list of image codecs that have additional library dependencies:
where processor is the is the CPU architecture of your target hardware (e.g., armle-v7)