When previewing the same report in the designer more than once, the report was rendered twice for each additional preview.
NullPointerException occurred when opening a report in the i-net Designer on Unix systems where no /media folder is present.
Welcome Page: It was not possible to open a report from the list of recent reports containing the character “#” in it's path.
SQL Editor: New line after the keyword “Select” was detected as error.
NullPointerException occurred if the i-net Designer was used as remote Designer (JNLP) and i-net Crystal-Clear was running on JBoss.
Memory leak in the Chart Properties dialog occurred.
A possible deadlock situation on opening reports was removed.
Viewing the preview of a report in the designer could lock up the designer for a while as long as the database server did not respond.
Wrong error message has been displayed if a “report as folder” was saved in a directory for that the user does not have the necessary permissions.
Better error message when a “Crystal Reports” report is opened in the Online Designer.
Entering numbers as parameter default values in the parameter field properties dialog had locale issues for locales which do not use “.” as the decimal separator.
Problem Finder:
has not kept the state of the warnings/errors when switching between main and subreport.
will no longer show incorrect warnings for on demand subreports.
shows a warning about an error in a property formula also, if the related element has been removed in the meantime.
IllegalArgumentException occurred when dragging a chart to the size of zero in i-net Designer.
Because of an error a rpt file was overwritten if the i-net Designer with called with “–new parameter” pointing to an existing report.
Java Bean preview in design view was wrong if a property formula was used for the scaling property of the Java Bean.
In rare cases an IllegalArgumentException has occurred when dragging an element in the design view to a position where it forced to snap into the next section.
Save button was not deactivated after the report was saved, if the edit modus of a text field was active.
The custom summary name in the chart properties dialog was overwritten by next usage of the chart properties dialog.
An exception was thrown while clicking on an error java bean (corrupted bean) in the design view of the i-net Designer.
Minor internationalization and localization bugs has occurred in the report viewer.
When editing prompts, if a cascading parent was chosen for a prompt which had a different table source, the OK button of the dialog could turn grey and not be re-activated.
Only changing the case of a parameter field's name caused the error “parameter field name already exists”.