CardExchange® Products Release Notes

Release 7.2.6.0 (October 30, 2013)

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

•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.

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

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

 

Release 7.2.4.0 (October 1, 2013)

•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.

 

Release 7.2.2.0 (July 25, 2013)

•Restored the lost translations from the previous version for the following languages: German, Spanish, French, Dutch, Portuguese and Romanian.

•When making changes to the database setup from the main window, like adding a storage item, these changes were not applied to the card template when opening it in the designer.

•The name-case formatting option did not change uppercase to lowercase when necessary.

•When opening a design that is connected to an empty database table or view, the database columns were not shown in the Data tab and in the drop-down menus on the Context menu, and any mappings were shown as {Missing column}.

•When specifying to print multiple copies in the print dialog, only a single copy is actually being printed.

 

Release 7.2.0.3 (May 1, 2013)

•When a shape was added, an empty insert-window was shown.

•When clicking on the Select-connection button in the Data menu and canceling the selection, the Edit and Remove-connection buttons became enabled, even though there was no connection.

•When there were non-existing database columns, selecting multiple objects could lead to a null-reference exception.

•If the My Pictures folder was not properly defined on a system, starting CardExchange™ resulted in a fatal error: “The type initializer for ‘CardExchangeDesignerX.cedImages’ threw an exception. Invalid URI: The format of the URI could not be determined.”

•When connecting to SQL Server and using a unique identifier as primary key, the following error could occur when opening or viewing the version 7 designer: “Conversion from type ‘Guid’ to type ‘String’ is not valid.”

•When navigating to a record for which no photo is available, with the background-removal option enabled for that photo, a null-reference exception occurred.

•Using fixed values for concatenation fields caused CardExchange™ to crash.

•It was not possible to do contactless and magnetic encoding in the same print process using a Magicard Prima 4 or a DNP CX-D80.

•In the properties window, the data for magnetic tracks was shown with escaped spaces (#32) and other special characters.

•Text data in magnetic tracks are now always converted to uppercase.

•Made sure that a template can be opened in the designer if there is no connection to the database.

•Adding a variable directly after starting up the designer caused a null-reference exception.

•Special characters in the start and stop commands of magnetic tracks were shown escaped instead of normally.

•When exporting an image from the application menu, the saved image format was not in accordance with the saved file extension.

 

Release 7.1.1.0 (January 2, 2013)

•Correctly included support for the OmniKey 5x27 reader.

•Trying to stack ellipses, rectangles or lines led to the error “Layout measurement override of element ‘CardExchangeDesignerX.cedRectangle’ should not return PositiveInfinity as its DesiredSize, even in Infinity is passed in as available size.”

•Make sure that any special characters in the string-type properties are handled correctly, including trailing carriage return characters.

•Trying to drag and drop a manual entry while that was being renamed led to the error “Dispatcher processing has been suspended, but messages are still being processed.”

•When a member function was called on a variable in an expression, the designer did not prompt for adding that variable.

•When editing the data definition in the designer, the changes were not processed by the four-clicks and were effectively undone when closing CardExchange.

•When starting the designer for a template with a MySQL connection, errors showed up and the records could not be read properly. The error message was similar to “You have an error in your SQL syntax; check the manual that corresponds to you MySQL server version for the right syntax to use near ’20 * FROM `table_name`’ at line 1”.

•Switching between records was very slow due to an inefficient rendering of the database tab in the properties window.

•When enabling a track of the magnetic stripe in the content tab of the properties window, the error "'~1%' is not a valid value for property 'Prefix'." was shown.

•When creating a new template in the card definition wizard, the data definition was not correctly associated with the new template.

•Templates with a database connection that contained a date/time field could cause errors when being loaded in a different culture than the one they were created in.

•When the mapping of a text or bar-code object yielded a numeric or date/time value, no data was shown in the object.

•When navigating in the designer, photos and signatures on the design were not updated, while variable images worked fine.

•When having an ODBC connection to a non-Microsoft type database, starting the design caused a SQL syntax error due to the fact that the “TOP 20” was not recognized. Since there is no generic ODBC syntax, the designer now loads the entire table in case of ODBC connections.

•When typing a script with new variables in the content tab of the properties window, the insert-variables dialog did not show when committing the change and the script was deleted.

•When changing the file extension of a photo to “Extension included in source value”, saving or printing the card resulted in the error “Value cannot be null. Parameter name: input”.

•When a rotated group was ungrouped, the grouped objects did not maintain their rotation settings. The same problem occurred with stacks.

 

Release 7.1.0.0 (November 20, 2012)

•After changing the language via the View menu, the sort order in the drop-down menus was not restored.

•Images with the extension *.tiff were not shown in the file dialog for selecting images.

•It was not possible to delete the expression for a layout condition.

•When closing CardExchange immediately after removing a photo using the Remove button in the Photo tab the fatal error message “A fatal error occurred in CardExchange. Object reference not set to an instance of an object.” was shown.

•When inserting new records into SQL Server from various work stations, CardExchange often selected the wrong record when insertion was completed. When trying to select already deleted records, this could even lead to error messages.

•Now, when a null field is send to a magnetic object it is just not handled instead of showing an error dialog, like previously.

•Editing, removing, copying and pasting photos and signatures did not always work correctly.

•Avoid saving properties with default values to the .cedx file.

•Corrected the image background of the button “Previous record”.

•When changing an image mapping from Photo to Script and then back to Photo, the database-column drop-down menu was not shown anymore.

•Positioned the magnetic stripe on the top of the card instead of the bottom.

•Scripts that were defined on attached properties (Left, Top, Printability) were not executed during printing.