TSC / CCS / MCS

Test - Integrate - Control

Update to Qt5.4

Tested builds using Qt5.4 are now available
For a few weeks our daily builds have been using Qt5.4, now there is a formally tested release.

Our main interest in Qt5.4 is that this release includes dynamic selection of the most suitable OpenGL rendering back end, using either hardware or software rendering. More customers today are opting to virtualise their CCS, and to access the CCS via a remote desktop protocol or thin client. For our customers this can have significant economic advantages (reduced travel, reduced mission-dedicated infrastructure). However some parts of the CCS software make use of graphic-intensive OpenGL-accelerated displays.

Previously, some features using OpenGL would not work on low-end hardware or using basic remote desktop protocols like RDP. Typically this would be seen as a QML or AND view appearing as a blank screen. This could be worked around with high-end protocols (e.g. PCoIP), or this could be configured by different compilation switches in Qt. To allow both options (hardware acceleration or software-only) we would have had to deliver one of each type of build (thus doubling the matrix CCS/TSC/32 bit/64 bit) which would be confusing for customers as well as difficult to manage.

Qt5.4 selects dynamically which is the best rendering back-end to use, including software emulation. This means that interfaces using OpenGL (such as QML) can work, ….albeit slowly…. , over remote desktop protocols such as RDP by rendering in software.

At the same time, the desktop and installer icons have been updated to be consistent with the new-look CCS website.