AXWare For Windows v5.30.x

Version 5.30.008.013 - Pre-Release

New Functionality

Enhancements

Fixed

Version 5.30.007.004

Fixed

This update should immediately follow 5.30.006 due to the nature of the fixes listed below: Not all timers are affected: non affected timers include the AC4, non-Chrono mode JA Circuits, and  all other Net Time based timer.

Version 5.30.006

New Functionality

Enhancements

Fixed

Version 5.30.005.025

New Functionality

Enhancements

Fixed

  • Print Labels
    • Registration Labels - printing Registrations labels defaults to the continuous style of labels which were directed at non-label printers. Workaround: set the default printer to the Label Printer and print labels as necessary.
    • Bar Code labels - the continuous printer support was defaulted to label printers rather than non-label printers.  Thus the Barcode/Continuous Printing setting did not target non-label printers.
    • Note: Continuous Label printing is utilized for tractor fed printers or special sheet fed labels. The continuous support utilizes 1 column of continuous labels (not to confused with sheet fed labels which have multiple columns).
  • Bar Code Value generate - when Unique Bar code value is ON and you were editing or copy & Inserting an entry,  an extraneous message was displayed indicated that the Bar Code value is not unique (but was auto-generated).  This message no longer occurs.
  • Staging Grid:
    • TTOD - Clear Time or Reset Finish - if a car had recorded a TTOD (overall or for a particular group), Clearing the Time or executing a Reset Finish (either from the software or as a Timer function) would not reset the TTOD for that entry.  The TTOD would update only when a new TTOD was recorded, or the Re-Accept All Runs for Current entry was executed from the staging grid. 
    • Un-registered cars - the car number was ignored for un-registered entries if the Class field was blank. This could occur if the Unique Car Numbers is Active and entries were staged but not registered. When the event was reloaded, the class field would remain blank for any un-registered entries.  Recover using versions v5.30.005 or newer, or manually enter the car numbers based on the *.st1_log file.
    • Editing Re-Runs - when editing a Re-Run for an entry (either deleting or changing it to a cone count), it was possible for the run to not be re-consolidated. The run number was not re-calculated and thus the run would appear to be ignored.
    • Shift-F3 and Shift-F4 - search for entry up and down direction - needed to be swapped directions. Shift-F3 is Up, Shift-F4 is down.
    • Rare condition but possible - If an entry contains a Blank Run # (but not for RERUN), and that entry is manually entered further down in the Staging Grid, the Run numbers will start at Run #1 for the new entry. It is expected this occurs mostly for non-registered entries that are staged regardless.
  • Class Definitions - the incorrect ToolTip was provided for the Move Up/Move Down control.
  • NCCC Points Settings:
    • Since Race Points do not necessarily correlate to a Membership File, access to the Points Settings is now possible without associating the Event with a Membership File.  However, when a Membership File is associated with the Event, Points Settings can only be manipulated from within the Membership File, insuring consistency across events.
    • Membership File Settings - when a Membership File is associated with an Event, and it is change to a different membership file via the Modify Event Attributes, the points settings were not refreshed.  As a workaround, when the Event was saved and reloaded the settings were properly associated.
  • Edit/Insert/Copy & Insert Dialog - can't save a record after re-classing it via the Dialog's Re-class Button. The warning that the entry already exists was displayed.
  • Update Points
    • When using Percentage based points control, if the order of the Updates Points Dialog is anything but the default order (when the dialog loads), the calculated points may generate values exceeding 100.00.
    • Minor modifications with respect to Status bars to indicate the completion of the execution of the Points Update.
  • Heat Assignments By Car Number - the Active Heat Pull-Down in the Staging Window Did not contain the proper number of heats nor was it updated following Heat Assignments By Car Number .
  • Label Print Templates - if the Width of the columns was not specified in the Print Template for the respective Label, the template would be shifted down 1 row. This could cause problems when printing with these templates (crash could occur).  Although no longer a problem, it is recommended to provide column widths for all label templates, otherwise default column widths are used, which may cause formatting problems (dependent of the size of the label).
  • Event Settings - when Unique Car Numbers is turned off, the Unique Car Numbers within Pax Class was not reactivated unless the Dialog was closed and reloaded.
  • Re-Class Dialog - the class selection pull-down list was in advertently automatically sorted alphabetically.  The list should be identical to the Insert and Insert & Copy pull down list, which can contain either alphabetically order classes or in the 'class definition' sort order (respective to the setting Pull-down Sort in the Class Definition Dialog).
  • Networking:
    • Active timers, designated by T-1, T-2..., in the Staging Grid where being sent to Networked Clients.  This is unnecessary and no longer occurs. This only impacts configurations that utilize timers that have individual start and finish trigger data.
    • Admin Client - found conditions where the data from the Timing Server was propagated back to the Timing Server causing unnecessary data exchanges. In addition, if time-slips were being printed, 2 labels could be printed as a result.
    • v5.30.005.019 introduced a networking data exchange loop that would force the Registration, Admin Client and T&S to exchange data continually. This would eventually overpower the clients. The only work around was to terminate the clients. 
    • Data Exchange - Overwriting Staged Entry - when a car was overwritten either via the Class Tree View or manually updated, the first message sent to the other clients was not required and could cause a redundant data exchange between the Admin Client and the T&S Server.  Data is now sent only when necessary.
    • Deletions - using  the Delete Current Entry function in the staging grid could leave the car number on the very last line, especially if the Admin Client is running. If the Admin Client is not used, the problem did not surface.

Version 5.30.004.015

New Functionality

  • Time Slips - Print Templates for Time Slips now support 2 extra fields: today's date (which includes the time), and blank row.
  • Penalties Included in Time - a new penalty option (controlled via the Penalty Settings), allows the cone counts to be included each Run Time. The cone counts will be added to the Time displayed in the Standings Grid, and all affected reports.  The staging grid is un-affected (i.e. it will always contain the actually time and penalty), but Time Slips will contain the conversion. In addition, if this option is active a note will be printed on all reports to indicate that the calculation is in affect. 
  • Stand Deviation - Consistency Analysis:
    • Runs can now be analyzed using a Standard Deviation formula using 2 methods. 1 is a standard deviation formula, while the 2nd uses the average of all the runs + the standard deviation.  Only valid runs, and those with pylon counts are used in the calculation. DNFs runs (course not followed penalties) can be assigned a explicit time value (see below).  To activate the standard deviation, one of the optional headings must be set to "Std.Dev".  If found the Timing Menu will activate 2 functions that allow you to generate the Standard deviation values.  
    • DNF (course not followed penalties) are assigned a specific Run Time to help control the generation of the Standard Deviation.  This value is set in the Penalty Settings.
    • "Std.Dev" - when sorting the grid on the Std.Dev column, it will automatically the values within each class, thus the results are Class Specific.
    • "Consistency Pnts." - a new data column, when present, will force Points to be assigned to each entry. The points are assigned starting at the 2nd position points and only 4 deep.  The points are automatically assigned if the column exists and based on the Std.Dev results generated by the Timing/Calculate Standard Deviation command.
  • Checkin data column added to Registration/Standings Grid:
    • provides access and control for worker check-in. The Worker Assignments and Registration grid keep this column synchronized. The Checkin column can be used from the Worker Assignments reports (heat based) or directly from the Registration Listing.  A custom template can be created to contain this column on any desired report (ex: registration listing).
    • Automatically DSQ non-checked in workers - a new Work Assignment control allows you to selectively DSQ all entrants that are not flagged as Checked In.  When the  "Checkin" flag is no set, the entry will be DSQed automatically if they participated in the event..
  • Dropped - iCard(tm) Support - due to lack of interest.

Enhancements

  • Networking
    • Performance enhancements -  minor Improvements were made to separate the output and incoming data feeds. Prior to this, the same process managed both of these feeds and as a result reduced performance slightly. Splitting up the process has dramatically increase the processing speed.
      •
    • Announcer Clients - the synchronization of the Staging and Registration/Standings entry (controlled by the Setup/Options/Auto-focus Registration On Timing setting), no longer sets the auto-focus when data is received from the Timing Server. This allows the synchronization of the entries to be controlled directly from the Announcer Client only.  Prior to this, entries were synchronized when an entry was Staged and when timing data was recorded on the Timing Server. Something undesired for Announcing.
    • Admin & Announcer  Clients - reduced some extraneous Networking logging which slightly improved performance.
    • Removed additional redundancies in data exchanges, especially between the Admin Client and Timing Server.
    • Print Barcode Labels or Registration Labels - during active Networking sessions could print data for the car not selected. This is especially true if cars are being registered on one client while editing an entry on another.  A potential focus change (selection of a different car) in the Registration grid will cause the incorrect data to be printed when using the Print Barcode or Print Registration Label buttons. Labels, including barcodes were printed based on row selections. This revision uses a different mechanism (not longer based on row selections), so this is no longer a problem.
    • Registration Column Sorting - if a column other than the Total data column was selected, the sorting could flip order based on the Ascending or Descending selection (it would by default sort Ascending in most cases).  This is no longer the case, the sort remains intact until changed or automatically reset to the Total time column if active timing data is being received and processed.
  • Events - Insert New Entry & Re-Class - the Re-Class function could inadvertently be executed without providing a source class and car number.  Normally both are required for this operation.  As a side affect, and an undesirable one, if the Re-Class is attempted immediately after loading the Insert New Registration Entry, the car number is not specified (blank in v5.30.003+). This is an incomplete designation and as a side affect the last entry in that class may be updated incorrectly.  As of this version of the product, the Re-Class function will only execute when both the Class and Car Number are specified.
  • Find Dialog - made the settings in the Find Dialog persistent.  When the settings are modified for a search, those settings will remain until changed.
  • Insert/Copy & Insert Dialogs with Unique Car Numbers - minor improvements made to reduce beeps and messages that indicated data was modified but not saved.  These messages would occur if the car number was modified in for the selected class, and data had been saved for the prior entry.
  • Registration/Standings Grid:
    • The First and Last Name columns can now be sorted separately. Prior to this the if the Last->First Name order was selected, sorting on the First Name would automatically switch to Last-First Name sort.  This is no longer the case.
    • Several Columns can how sort in both Ascending and Descending order (these include, First Name, Last Name and several others). Prior to this, these columns were ordered only in Ascending mode.
  • Importing into & Auto-populating Events:
    • Bar Code values - the setting for Bar Code values may differ between the Membership File and the Event file. Effort should be taken to keep both the Membership File and the Event settings synchronized but if they are not, the import will enforce the Event File settings and will regenerate the Bar Code Values accordingly.
    • Data columns like City, State and the Street address can now be defined in the Event Optional Data Columns and import from Membership data or from other import data sources.  This requires that the Optional Columns are configured for the Events. Note: the definition of Optional Columns may differ between Membership Data and Events. Thus if one of the Optional Data columns is "City" it should not be defined in the Membership but ONLY in the Event file.  "City" is a based data item in the membership data and would be redundant if defined in both files.  Alternatively, if the City and State are needed in the Event data, the pre-defined "Location" field can be activated and used as necessary. In addition, the Optional Data columns can be printed by modifying the appropriate Print Template.
  • Membership File:
    • Print Reserved Entries - an updated Print/Reserved Car Listing option now allows printing of All entries, members Only, or non-members only. Reminder: If you sort the Membership Grid on the Class, the HTML reports also contain bookmarks for each class.
  • NCCC 2006 Report enhancements - updated the NCCC Final Summary to reflect the data items that are required for 2006. The NCCC Final Result heading and names of some columns were changed. Minor impact.
  • Staging Grid:
    • Entering Class - did not accept non-alphanumeric characters, thus '-' (hyphen) was not accepted.  This could cause problems when entering classes that have imbedded hyphens.

Fixed

  • Print Templates
    • Time Slips - the Penalty Field was missing from the pull-down selections.
  • JA Circuits - [Net time mode only] - the reset finish from the timer did not remove the last recorded time.
  • Networking:
    • Scanning Registration Mode - Registration Client/Admin Client: - if the Scanner is being used Register entries, the registration was not propagated to the Timing Server, thus the entry would appear as not being Registered on that machine.
  • Re-Classing - if you have Unique Car Numbers active, the Re-Class function would  complain about an existing entry if you attempt to change the class of the entry.
  • Work Assignments - when selecting work assignments in the dialog the Heat # would be set to "na" rather than the heat that the entry belongs to. Workaround: set the work assignments and then reload the Work Assignments dialog.  This would reset the Heat #'s to their appropriate values.
  • Insert New Entry & Bar Code Values - when unique bar code values is active, the Bar Code value may skip over the next appropriate value (they are normally assigned sequentially).
  • Networking:
    • Unique Barcode Values - if Unique Bar Codes are being generated, it was possible to create values on the Registration, Admin Client, and Timing Server that already existed. This was not a problem if the Next Bar Code value (the seed for Bar Code values) was set differently in the Bar Code Setup.  Generally if each client has a difference of 1000, conflicts are highly unlikely.  However, if the seed (Next Bar Code value) was identical on all machines, then collisions could occur and thus re-used Bar Code values.  As of this revision, the Registration list is now actively checked to make certain a bar code value is unique. If updates from other nodes are received, a conflict is now avoided.
    • Staging Grid & Admin Client - if an entry is modified by deleting the Class or Car Number on the Admin Client, (by blanking it out or using the DEL key), the Timing Server received the data correctly but did not execute the additional operations needed to update the timing data for the original car. In addition, the data was not relayed correctly to the Announcer Clients.
  • NCCC
    • Insert New Entry Dialog:
      • When the class is selected, and a TAB not pressed, the first class in the Class Pull-down list will be designated for that entry. Pressing the Save again will force the proper class to be saved.
      • Dialog would complain about "data being modified but not saved" too often.  This started due to the modifications in 5.30.003 and the support of a blank car number. The message was not appropriate and pressing the "OK" was necessary to continue processing the new entry.
      • Barcoding - with Barcoding and non-unique car numbers is active, whenever a bar code value had to be regenerated for the same entry (when the class or car number change during editing), the new class may not be used.  The old value was retained.
    • Start New Event - if the Browse button is pressed to select a membership file to associate to the event, the data items that were entered in the Start New Event dialog will be cleared. Workaround: select the membership file before entering any other data for the event.
  • Bar Code Values & Unique Car Numbers - a reformat on the Bar Code value would occur when data was loaded, imported or merged.  It should only occur for Unique Bar Code Values. In addition if the NCCC version was active the Ladies designation on the Bar Code could be removed.  Both Events and Membership Files were affected.
  • Event Settings - as of v5.30.002 the Lapping Mode and RallyX mode radio buttons were reversed in function. Then Lapping Mode was selected, RallyX would be checked and vice versa. A minor Windows Resource error, they now function as expected.

Version 5.30.003.015

New Functionality

  • Log Files - for networking and trace logging, all network nodes now have their own log files. This includes staging and registration files, respective to the network mode. This provides a more explicit set of data interactions respective to each Network Client (including the Timing Server).
  • Printing:
    • Two new date options have been added to the Print Templates. Intended to be used for Bar Code, Registration labels and membership labels, you can now print labels with Today's date or the Event Date. 
    • Print Templates for Labels - label based templates (Bar Codes, Registration, Mailing etc), support multiple columns and width control.  The widths of the columns is controlled by a 'Width' row that is visible in the Template Table.  If the width row in the table is blank (i.e.: no numerical data specified), the default widths will be used, which for labels is 29 characters). Note: Please test your configurations since the print region is determine by the overall size of the label, it is not possible to configure the labels that will run past the print region (and clip your data). Also: This process is not provided for any other reports. The headings on the first row dictate the width of all following columns. In addition, the widths are only relevant to printed data, not HTML output.
  • Networking:
    • Clarification: Since it's possible to obtain un-synchronized data between the Timing Server and Clients, processes have been put in place that inform you of this condition.  In all cases, un-synchronized data results when operations have been executed on the data while the Networking mode was not active. If this occurs no Networking commands are issued and the modification is considered local to the loaded data set.  Since the Timing Server is the key to controlling the data set, it has the final control of the data set as well.  If data was modified by a client (and if not in a Networking mode), the updates from the Timing Server and the Client will not be synchronized.  It is important to always switch the Client into the respective Networking Mode prior to making any data modifications. 
    • Network Synchronization Dialog - a Network Synchronization dialog will be display when un-synchronized data is detected. The dialog will list all conflicts and allow you to force a -re-synchronization (mentioned below), as well as functions to clear the conflicts from view.
    • Auto-synchronization: the software now offers an auto-synchronization process that detects if data becomes unsynchronized.  If it detects this condition, commands are issued to the Timing Server to save the event, and the affect clients are send a Reload command.  Please refer to the Documentation for more information.
    • Starting Network Clients - when a Network mode is activated (except the Timing Server), an auto-synch command is automatically sent to the Timer Server.  If the Server detects that the Client requires Re-Synchronization, an event Reload command is issued to the Client.
    • Request Re-Synchronization - a new Network Menu command that allows the user to request a network Re-synchronization check. The command is sent to the Server and if data has been modified or the number of messages expected is different from what is supplied, a re-synchronization command will be issued.  If data has not been modified, the command is cancelled.
  • Event Window Views - the splitter Window which dictates the size of the Registration and Staging Windows is now saved for all Networked Modes.  This means that if you move the splitter divider, this location is retained for future invocations of that mode. This setting is a GUI preference and is not contained in the Event file.
  • Find Dialogs - introduction of floating Find dialogs. These dialogs allow you to find items in a more interactive manner. The Find dialog will remain active (visible) until the Cancel button is pressed, and provides options for searching up/down, searching a single column or all columns, case sensitivity and exact data matching (full cell match). It also allows you to change the selected column to search while the Find dialog remains active.  The toolbar search control retains it's much simpler search functionality.
  • Event data Importing/Merging - when importing and using the Merge option, some columns would appear to not import based on the column order. This is no longer the case. 

Enhancements

  • Printing Labels - printing Barcode, mailing, or registration labels now turns off the Print To Text File or Print to WEB (HTML) file automatically.  Prior to this printing these labels would attempt to print to the selected target medium, and in many cases resulting in a program crash (Bar Codes and normal text file output is not compatible due to the nature of the bar code image).
  • Column Preferences:
    • Events: All column preferences are now persistent (saved as preferences). Prior to this, the timing data columns were automatically re-enabled when an Event was loaded (and were not persistent).
    • Membership File: the points data columns were treated in the same manner. All columns now support persistent points column preferences.
  • Loading Membership Files - it is possible to recreate a membership file by copying the control file (*.MCF) and the data file (*.MBR), however, it this can cause a mismatch condition whereby the number of events (and other settings) become out of synch. To fix this condition, the loading of the file has been modified to detect that condition. Note: Regardless of this workaround, it is important to move/copy both the *.MBR and *.MCF files together.
  • Insert/Edit/Copy & Insert:
    • The initial car number has been set to <blank> rather than "0".  This should help clubs that use car numbers = 0.
    • Improved the indications when data was flagged as modified prior to printing labels or attempting to exit the dialog.
  • Re-Classing Entries - if a conflicting entry is found, the driver name of the existing entry is display in the Re-Class dialog.
  • Networking Commands - the Add/Modify indications during networking (in logs and status windows) was split into Add and Modify commands respectively. This improves the visual feedback on what actions are being carried. To see the actions, the Registration status window must be visible.
  • Networking
    • Exit Application - no longer get prompted to Save event data when closing the application via the 'Close Application' button (X in the application Window), if a Network Client is active (does not apply to the Timing Server).
    • Improved program responsiveness during heavy network loads. No noticeable different will be seen during normal interactions.
    • If Setup/Modify Event Attributes were selected, an update notification was sent to all clients even if no attributes were modified. Also Bumped Class support was not exchanged between the clients.
    • Clarification: it is currently unwise to change the type of Bar Code values while in Networking. It is recommended to exit networking, make the appropriate changes, save the event and restart the networking clients. This may change in future releases but this functionality is viewed as a fundamental event (and membership) file setting, and the decision of the Bar Code type should be made ahead of time.
  • Points Update - if any criteria is now changed, the 'Submit' button will be disabled until you press the 'Refresh' button.
    •  
  • Event Export to Membership File:
    • If any criteria is now changed, the 'Submit' button will be disabled until you press the 'Refresh' button.
    • If Bar Coding is active and using Unique Bar Code values, bar codes are automatically regenerated when duplicates are found (in the target Membership File) and the entry belongs to a new class. This can occur if entries have been reclassed in the event. When Unique Bar Code values are used, the value sticks with the entry. This is not desired when exporting however, especially when the Bar Code already exists. Regenerating Bar Codes keeps the entries unique in the Membership file.
  • Import Members Data - if any import criteria is changed, the 'Import' button will be disabled until you press the 'Refresh' button.
  • Print Processes - improved process control  when other actions are pending (like network activity, pending data updates, timing events etc). Data related actions and printing are more independent processes.   This only affects the actually generation of a print job, not the actually printing.
  • Printing Templates:
    • The maximum number of rows that may be configured has been increased to 6 from 4.
  • Staging Log File - added more logging output to the log file and reduced redundancies by utilizing independent traces files for each client (respectively). Prior to this, the tracing file was shared by the Admin Client, Timing Server and the Announcer Clients. The separate log files reduce the size and provide more explicit content to the trace file. Please see the documentation for File Type descriptions for more information.
  • Re-Classing - a single operation is not logged both in the trace files as well as exchanged between networking clients. This provides a single record of information that contains both the old and the new classing for each entry.  Prior to this, two records were used in the exchange. This affects Networking as well as Registration Logging and recovery.
  • Membership Bar Code Labels - certain data columns were automatically centered, which is no longer the case.
  • Registration/Membership Grid Field Overlap - the overlapping functionality of data cells is now disabled. Inherent to the Grid, data was displayed in adjacent cells if the right side cell was empty.  This was undesirable when columns are hidden and would appear as if random data was being displayed. 
  • Networking & File SaveAs - prior versions required you to Disable networking before properly saving the Event.  This version provides a File SaveAs that does not require the Networking to be Disabled, however, Networking becomes active for the new event file.  The File SaveAs can be used to 'save' an event to a backup location during the event. It is important to load the appropriate file to continue Networking.
    •

Fixed

  • Unique Bar Code Values - when the Unique Bar Code values is selected, and when networking clients or when using several machines to manage the data, the values could get out of synchronization and values could be reused.  This version introduces a dynamic verification of the Bar Code value and if found to conflict, automatically regenerates a value when either pressing the "Avail #' button or the Register button in the Insert/Copy & Insert dialogs for events.   Unique Bar Codes are also managed during export and points updates (as mentioned above).
  • Print Templates - using the "Class, Number" data field in a template will result in the class being printed 2 times (and without the car number).  The problem turned out to be a build problem.
  • Re-Classing Entries w/Unique Car numbering in Pax classes - when the "Use Unique car numbers within Pax classes" is in affect only a base class change is desired, an error would be reported stating that the entry already exists.  It should permit the operation. Example: it reported the error when trying to re-class NBS 45 to NCS 45 (but should not have).
  • Networking:
    •  Reloading Same Event - Reloading an event or closing the event could at times force a 'Save dialog' to appear when in running a Client Networking mode. This was mostly evident when reloading the event using the File/<select same event> command.  Clients should not pop that message up since the Timing Server is responsible for saving the event.
    • Admin Client - minor changes for improved performance and function.  Also possibility of ending up with a redundant exchange of messages with the Timer Server when the timing data was modified. Only work around was disable the Admin Client and turn it on.
    • Inactive Admin Client - it was possible for the Admin Client to end up in an inactive state if the Admin client was repeatedly Enabled and Disabled.  Workaround for this condition forced the reload of the Event and re-enabling of the Admin Client.
 

Version 5.30.002

New Functionality

  • NEW BASE INSTALL for 2006 - this version contains all the updates in the 5.20.x revisions and any additions mentioned for this release.
  • Find, Find Next and Find Previous commands have been added to the Edit Menu. The Find command will pop up a dialog box that allows you to enter the text to search.  The Search functionality is identical to the Tool Bar - Find control and will execute in the selected column of the active grid (the one in focus).  Hotkeys can be used to access the functions: Find = Ctrl-F, Find Next = F3, Find Previous = F4.
  • Print TTOD In Heats - new Print setting that allows to toggle the printing of the TTOD listing in each Active Heat. Some clubs only want the TTOD listing after all the heats have been completed.

Enhancements

  • Pax Class field was made a bit later in all dialogs.
  • Label Printing - when printing labels from controls that display a print dialog, the dialog will use the Orientation as set in the Print Settings.  
  • Several menus have been updated to reduce duplicate menu keys and to support the new Find functions mentioned above..

Fixed

  • Different Users when different users log onto a PC and attempt to setup their own preferences, the original settings created by the user that installed the software, are not available.  Workaround: Exit the application and login as the different user. Copy the axwarew.ini to a new file name (ex: axwarew_aved.ini). Login, start the application, exit the application, copy the saved axwarew.ini file, (i.e. axwarew_saved.ini), over the existing axwarew.ini, restart the application, and immediately load execute Setup/Import Settings to import that settings in the axwarew.ini.
  • Print Templates and specifying timing based columns in the template - the timing data columns are automatically controlled during normal printing (specifically "Total" and "Diff."). When templates included either of these data columns, redundant data was.

Prior Version Release notes:

 Copyright © 2006, AXWare Systems, All Rights Reserved.