The class ReportViewChangeListener was not visible in the file: CC-Viewer.jar.
The export drop down button could be active even if all exporting was disabled for a certain report.
While using embedded fonts, certain letters could (in rare cases) disappear from the displayed text in the report when reloading rather than refreshing the report (such as when previewing the report in the designer). This occurred mainly in the designer, and only if the report changed in such a way that a font changed and less letters were needed.
Loading a jar file which was not a Java Report Archive did not show a readable error message.
Sub-report prompts were not shown as such. They now again show the name of the sub-report in parentheses behind the prompt name in the viewer's parameter request dialog.
The prompt dialog had graphical glitches if some prompts had a description while others did not.
When closing a window which held a ReportViewer, the ReportViewer would close all report views when getting the “windowClosing” event. However, if after this event the window was not closed after all (i.e. if the window close was canceled), the Viewer had already closed its report views too soon, leading to a grey viewer panel. Instead the Viewer now listens for a windowClosed event to then remove its views.
A memory leak in the Viewer was fixed when closing and opening many viewers from within the same application.
In rare cases in the report designer with multiple pages view, the report viewer could end up showing white pages only until the report was refreshed.
For multi-column reports, an empty group tree was shown in the viewer. Now the (empty) group tree is no longer shown.