Viewing bookmarks in the browser – a new function now allows to easily open more working sets and simply switch between them by clicking on the title of the bookmark
Volume data segmentation support – by drawing an area in one of the basic projections, it is possible to remove an unwanted object from the volume data to easily hide the CT table, which distorts the MIP or VRT display. Segmentation can also be performed automatically based on density, for example by hiding bones in volume data
CD VIEWER improvement – the image viewer that can be burned to a CD has several other improvements. These include for example automatic termination of the application when closing the window of the default web browser, as well as checking for duplicate launching of the application
Image rendering optimization – owing to the availability of the new WebGL2 extension in Chromium-based browsers, we were able to implement a new display that uses data directly in the binary form in which it is loaded from DICOM images. Therefore, there is no need to convert any image data to a format that can be used directly by the graphics card. As a result, even on slower computers or computers with software emulation, the image display is even smoother than before
HTTP / 2 support – HTTP / 2 is a new version of the protocol for communication with the web server from 2015 which eliminates a number of shortcomings of the HTTP 1.1 protocol from 1997. The protocol is binary and has less overhead so the transfer itself is a bit faster. The implementation in browsers strictly requires encryption and, in addition, individual requests are processed in a stream, so the protocol has a better response when retrieving a larger amount of data. However, the main advantage for DPGW is that all major browsers allow only 6 parallel data transfers from one site at a time when using HTTP 1.1, while when using HTTP / 2, up to 100 data transfers from one site can be processed at the same time. The version of the protocol is automatically agreed on by the parties, so if there is, for example, a proxy in your network infrastructure that does not know HTTP / 2, HTTP 1.1 will be used automatically
