<< Click to Display Table of Contents >> Navigation:  CardExchange® Producer Release 9.x > Designer > Bug Fixes

Release 9.2.1.34 (May 6, 2015)

•When using background removal in combination with stretching mode “None”, the DPI property of the original image was not respected and assumed to be 96.

 

Release 9.2.0.32 (March 9, 2015)

•When using the GDI + print engine, printed text was of a lower quality.

•When using the GDI+ print engine, magnetic-encoding commands were not processed by the printer.

 

Release 9.1.2.30 (January 22, 2015)

•When having an object with a border of different thicknesses on various sides, using the ribbon buttons to add a border to another side caused the error: “Conversion from string "" to type 'Double' is not valid. Input string was not in a correct format.”

 

Release 9.1.0.24 (October 6, 2014)

•If the storage item name for a photo, signature or biometric image was different from the column name, the user was asked erroneously to create a storage item when closing the designer.

 

Release 9.1.0.22 (September 10, 2014)

•When changing a text-box or bar-code mapping to Fixed value, canceling the confirmation message cause the message to be shown again. When canceling again, the drop-down menu remained on “Fixed value”.

• When modifying database connections, manual entries or contactless definitions, the drop-down box for the image mappings was not updated (only available in the Ultimate edition).

•For the lower editions, the non-licensed image types (biometric, signature and variable) were not appropriately hidden.

•Changes of the image type of an object that was originally created as a photo, signature or biometric image in version 9.0 or earlier were not stored when saving the template.

•Network printers with double backslashes in the beginning of the name were shown with two empty upper categories in the printers tab and print-to button.

 

Release 9.1.0.0 (September 1, 2014)

•If the default template font was set to a non-default value, this setting was not respected when printing, causing text objects use the default font instead of the default template font

•When adding variables or macro commands in the page setup, a null-reference exception occurred.

•If the first field of a concatenation was empty and the fields were separated by spaces, the resulting concatenation started with a leading space.

 

Release 9.0.8.17 (June 11, 2014)

•When dropping a database field on the concatenation button of a magnetic-stripe-track mapping, the field was not concatenating to the existing mapping but replacing it.

•When connecting to multiple databases and walking through the records in the designer, field values from secondary database were not cleared if no corresponding record was found in that database, causing the values of the previous record still to be showed.

 

Release 9.0.6.15 (April 10, 2014)

•Records with a null primary key were not excluded, causing empty records to be loaded from Excel files with deleted rows.

 

Release 9.0.3.7 (February 10, 2014)

•When an empty text object was changed into a concatenation field, a null-reference exception occurred.

•Any settings done in the designer’s print dialog other than the copy count were neglected.

 

Release 9.0.2.6 (January 1, 2014)

•When using the pre-rendering option in the page setup in combination with magnetic encoding, the magnetic stripe was always printed on the card.

•When creating a new data definition, the default save location in the file dialog was not explicitly set to the root of the data folder.

•IDP printers were not recognized as I&A Smart printers for the card-movement and magnetic-encoding commands.

•If a photo object was mapped to an empty binary field in the database, the point-to-file options were not disabled.

•When creating a new MIFARE® Classic or DESFire definition, the default save location in the file dialog was not explicitly set to the root of the data folder.

•When a storage item was mapped to the chip serial number in the designer, the chip serial number was not actually stored in the database.

•When starting the designer from the card-definition wizard and adding a MIFARE® Classic or DESFire definition, the definition’s file name was not shown in the card-definition wizard after closing the designer.

•Adding a MIFARE® DESFire definition to a new layout in the designer caused the error: "Cannot edit the card layout. There is no row at position 0." when closing the designer.

 

Release 9.0.1.5 (October 30, 2013)

•When printing via the GDI+, it was not possible to have different corner radiuses for the different corners of a single object. It resulted in the generic error “A StartDocPrinter call was not issued”.

•When printing via the GDI+, gradient brushes were not printed correctly.

•When selecting the mapping type Script for a variable in the content tab, the following error occurred: ‘…’ is not a valid value or property ‘Text’.

•Avoid that the designer window opens outside the desktop area.

•In the professional edition, a null-reference exception occurred when opening the page settings and clicking Add variable in the Variables tab.

•When printing via the GDI+ with a card-size setting that did not match the printer’s page-orientation setting the pages were not rotated in the same way as for printing via XPS. Now, the result with XPS and GDI+ is always the same and the printer’s page orientation is adapted to the card-size definition automatically.

•Manual-entry values were not communicated back and forth between the four-clicks interface and the designer.

•Pre-rendering produced uniformly black or white image when printing from the four-clicks interface.

•When a MIFARE® read item of the type text contained non-printable characters, the following error occurred when printing: “Error while printing the card. Could not print the card graphically. ‘X’, hexadecimal value 0xYY, is an invalid character.”