Release Notes for WinMark Pro version 188.8.131.5245
This file contains the latest release notes for WinMark Pro, version 4.6.2, build 5245.
WinMark Pro version 4.x software (WinMark_Setup.EXE) is intended for use only with Microsoft® Windows® XP, 2000, and NT4 operating systems using a PCI-bus Fiber Link Controller Card (FLCC). WinMark Pro version 4.x is backwards compatible with all previous SYNRAD DH, Fenix, and FH Series Marking Heads only when a PCI-bus FLCC is used.
WinMark Pro version 4.x software is NOT compatible with Windows 95 and is NOT compatible with Windows 98 operating systems using an ISA-bus Fiber Link Controller Card (FLCC). Version 4.x software MUST be used with a PCI-bus FLCC.
Pentium-compatible CPU, 233 MHz or faster
(300 MHz recommended)
64-MB RAM (128 MB recommended)
20-MB available hard disk space
One CD-ROM drive
Super VGA or higher-resolution display adaptor (16-bit or 24-bit SVGA color monitor recommended)
One open PCI-bus slot
Pentium-compatible CPU, 133 MHz or faster
20-MB available hard drive space
One CD-ROM drive
VGA or higher-resolution display adaptor (16-bit or 24-bit SVGA color monitor recommended)
One open PCI-bus slot
Pentium-compatible CPU, 90 MHz or faster
16-MB RAM (32 MB recommended)
20-MB available hard drive space
One CD-ROM drive
VGA or higher-resolution display adaptor (16-bit or 24-bit SVGA color monitor recommended)
One open PCI-bus slot
We recommend that WinMark Pro version 4 software be installed before installing the PCI-bus Fiber Link Controller Card (FLCC). Version 4 automatically loads the correct PCI drivers during installation. After installing the FLCC and re-booting the computer, Windows automatically detects new hardware (the FLCC) and loads the correct drivers without user intervention (except on Windows XP where the user needs to select the default choices on the dialogs provided when the new hardware is detected).
IMPORTANT INSTALLATION NOTE:
With Microsoft Windows XP, 2000, and NT4 operating systems, programs must be installed or uninstalled by an individual with Administrator privileges. Because of this behavior, WinMark Pro’s registry access permissions are initially set to Administrator by the WinMark installer when it sets the startup language. The installer does not support different access levels for registry keys so these must be changed by the program. It is therefore necessary to run WinMark Pro once as an Administrator before other, more restricted, users can run the program.
Version 184.108.40.20645 features include:
1. Added option for Truncated PDF417 barcode.
2. Added MicroPDF barcode.
3. Added ability to import vector files when measurement units are NOT in inches using a new property on the Tools/General Settings/Objects Defaults tab, Vector Import Scale Value. By default this value is 1.0; when Vector Import Scale is set to One to One and Vector Import Scale Value is 1.0, then vector files are imported at full scale in inches. If the drawing is drawn in millimeters, set Vector Import Scale Value to 0.03937008 (1/25.4), and then import the drawing. By changing the Vector Import Scale Value, you can import drawings that are drawn in any unit of measure.
Version 220.127.116.1195 features include:
1. WinMark sends only 16 bit marking data when an FH/Fenix lens is selected.
Version 18.104.22.16899 features include:
1. Fixed memory leak issue seen in build 4927 when entities where cut or copied to the Clipboard.
Version 22.214.171.12427 features include:
1. Added Copy/Paste and Drag/Drop functionality to allow importing objects from other programs. If the objects are represented as bitmaps, they can only be imported as bitmap objects. If however they are represented in a Metafile format, an import as a vector object can be attempted (with varying results). The user will be prompted to choose if more than one acceptable format type is available.
2. Text entities with just a single “l” or an “I” in simple stroke font end up having a width of 0 and are not shown on the screen or marked. This has been corrected.
3. Fixed the issue of having the ActiveX control opened multiple times in the same process. This occurs in VB when the IDE is open and the program is being debugged. The ActiveX control is opened twice and the symptoms of this problem would be that certain things would not work, like marking 2D barcodes.
4. Some parameters on the tracking tab were not initialized correctly when opening older tracking mark files.
5. Put in the build check feature when opening mark files so that a build 4927 file cannot open a file with a build number greater than 4927. This prevents an older version of WinMark opening newer files and possibly crashing the program.
6. Added Clearing Mark functionality under Tools/Application Settings. Set Clearing Mark On Begin Mark Session to Yes to perform a clearing mark operation at the beginning of a mark session. If set to No, the value specified for Clearing Mark Interval is used. The interval ranges from Never to once every 15,000 marks. We recommend that you set the Clearing Mark interval to 10,000. The non-lasing Clearing Mark function helps to achieve a continuous and evenly worn track on the bearing raceway and also redistributes lubricant along the bearing race. Implementing the Clearing Mark is the best thing you can do to increase the usable lifetime of the marking head since the bearings are the only part of the head that wear out with use.
Version 126.96.36.19988 features include:
1. Added the new Aladdin Hardlock driver and the new installation to the setup program. This fixes an issue with some machines and Windows XP Service Pack 2.
2. Fixed the No End Of Mark Response that some users were seeing.
3. Added error logging into the registry.
Version 188.8.131.5259 features include:
1. A bug in build 4733 and 4754 prevented the PDF417 barcode being generated. This bug has been fixed.
2. Two new properties have been added for the PDF417 barcode. The user now has the ability to set the security level, i.e. degree of error correction., The X/Y ratio, i.e. pixel height to width ratio, can now be chosen in the range 1 to 10.
3. The checksum property for those barcodes that either do not support a checksum or always use a checksum has been suppressed in the properties list.
Version 184.108.40.20654 features include:
1. In build 4733, older version mark files containing circles were not read properly, this bug has been fixed.
Version 220.127.116.1133 features include:
1. Spot marking style can now be used on barcodes, 2D barcodes and bitmaps.
2. The event builder I/O functions, WaitDigitalState, SetDigitalState, etc, can be used with multiple FLCC cards to expand available I/O.
3. A bug in the auto date function for the quarter is fixed
A new Application Setting has
been added to allow the marking head driver to be released during long marks.
This allows other applications, e.g. Internet Explorer, to run. However, if
this is enabled, marking can take much longer to complete. Time critical
marking applications should not enable this feature without adequate testing.
This setting has no effect when a tracking mark is being produced.
5. The Circle drawing tool has been enhanced to draw ellipses as well as circles. To force a circle to be drawn press the shift key while dragging the cursor. Alternatively, set the Minor Radius equal to the Radius to force a circle.
6. The barcode library has been updated. No new codes have been added but some minor bugs are fixed.
7. In build 4599 when using the 370 mm lens, a mark with x or y points greater than 3.2767 or less than –3.2768 would not mark correctly. This bug has been fixed
Version 18.104.22.16899 features include:
1. Text that is mirrored in the X-axis or Y-axis now rotates properly.
Version 22.214.171.12485 features include:
1. Very small-scale vector import files now import at the correct scale.
2. IGES files in units other than inches import correctly.
3. Vector files imported with the ActiveX control now import correctly
4. When optimizing vector files, during initial import or UnExploding, a progress bar is displayed at the base of the main window. This helps reassure the user that the program is working properly when a large file is being imported instead of appearing to have hung.
5. The ActiveX progress bar property can be used during optimization to show the import progress.
6. Optimizing can now be aborted with the abort key, i.e. ESC or the key that is configured in the ActiveX control.
7. Files with gradients can now be imported a little better than with previous versions. Try Camera.drw in the sample imports folder.
8. Sometimes lines are duplicated in imported vector files. This is an artifact of the vector file import filters that are used. There should be much better rejection of duplicated lines, etc, in this build.
9. Spaces in TrueType radial text were missing. This bug has been fixed.
10. Updating firmware from some fast PC’s, typically > 2.4MHz, could fail. This has been fixed.
Version 126.96.36.19928 features include:
Implemented constant velocity tracking. This encoder-less tracking feature provides parts tracking without a position encoder input. When the Use Constant Velocity Tracking property is Yes, enter the measured line speed as the Product Line Speed property. Use this property only with motion systems that provide a constant velocity.
Implemented Tracking with single-phase (non-quadrature) encoders. If your motion system is unidirectional, no reverse motion, a single-phase encoder input on IN1 provides sufficient motion data for Tracking. To implement this feature with a single-phase encoder, set the Use Quadrature Encoder property to No.
Added a new Drawing Automation property – On Abort Session. This event, which runs only if the mark session is aborted, provides a method to trigger an orderly shutdown or reset the marking system.
Default Tracking properties are moved from the Application Settings tab to the Drawing Defaults tab under the Tools/General Settings… menu.
The laser Power property can be specified in fractional values. Actual Power resolution is now 8-bit which translates to 0.4% steps.
Continuous scan bitmap and Grayscale images are now marked correctly when field transformation values other than default settings are specified.
Added a multi-line text entry dialog for the Barcode Number property when a barcode supporting extended character sets is selected as the Barcode Style. Barcodes supporting extended characters sets include PDF417, Extended Code 3 of 9, UCC-128, Code 128 (all 128 characters), and Extended Code 93.
Improved Spot Marking Style functionality. Spot separations along continuous polylines mark more uniformly.
Implemented fractional angles (to 0.01 degrees) for vector object rotation. Bitmaps still rotate only in 90-degree increments. The ActiveX RotateSelection method is unchanged – only integer rotations are permitted.
Added a new Auto
Text Type choice – From Another Object and a related property – Assign
From. These properties allow you to link, or assign, the text caption from
one object to another object or objects. For example, this feature can link
serialized barcode data to a human-readable text object, so that sets of data
Note that WinMark Pro will change the marking order of linked objects to ensure that serialized data and derived data correspond as the mark is made.
For example: Barcode1 is linked to Text1, which is serialized and updated before marking. In this case, Barcode1 must mark after Text1 because the full automation sequence is:
Restore saved data to Text1 - done in OnBeforeMarkSession [data = 1000]
Increment Text1 
Save Text1 
Mark Text1 
Assign Barcode1 value from Text1 
Mark Barcode1 
If Barcode1 were allowed to mark before Text1 the following would happen:
Restore saved text to Text1 
Assign Barcode1 from Text1 
Mark Barcode1 
Increment Text1 
Save Text1 
Mark Text1 
When Execute Auto Text When is set to After Mark, the opposite applies, i.e. Barcode1 must mark before Text1. If WinMark Pro changes the marking order, WinMark displays “Mark order changed.” in Launcher’s Mark Log window.
Added GetHeadInformation ActiveX method. GetHeadInformation returns Card type, Head type, Data type, Firmware version, and PCI version data as integers. Integer results correspond to the following values:
Card type: 1 = No Card;
2 = DDA06 (DAC) Card;
3 = ISA-bus Fiber Link Controller Card (FLCC), talk only;
4 = FLCC, talk/listen;
5 = PCI-bus FLCC.
Head type: 0 = no data (head not connected)
1 = SH or Unknown;
2 = DH;
3 = Fenix Index;
4 = FH Index;
5 = Fenix Tracker;
6 = FH Tracker.
Data type: 0 = no data (head not connected)
1 = 12 bit data;
2 = 16 bit data.
Head firmware version number: x. (0 if head not connected)
PCI card revision ID: x.
Format the control as:
GetHeadInformation < Card ByRef Integer, Head ByRef Integer, Data ByRef Integer, Firmware ByRef Integer, PCIrev ByRef Integer > STRING
Head, Data, and Firmware values will return as zero (0) if the marking head is not powered up or not connected to the FLCC.
Dim Card as integer ; the FLCC card type code as listed above
Dim Head as integer ; the marking head type code as listed above
Dim Data as integer ; the data type used by head as listed above
Dim Firmware as integer ; the marking head firmware version
Dim PCIrev as integer ; the PCI-bus FLCC firmware version ID
Dim LensType as String ; the lens type string (e.g. “FH/Fenix 80 mm” or “SH/DH 200 mm” as stored in the computer’s System Registry.
LensType = mh. GetHeadInformation Card, Head, Data, Firmware, PCIrev
Added ReduceColorBitmaps ActiveX method. Format the control as:
ReduceColorBitmaps < none > BOOLEAN
Performs color reduction process on the currently selected bitmap (greater than 1-bit depth).
A TRUE returned value indicates successful completion of the method. A FALSE returned value indicates either that an error occurred during marking or that the mark was aborted. See GetMarkErrorCode to determine which error occurred.
Added AddLineEx ActiveX method. Format the control as:
AddLineEx < ObjectName as String, x1 as Float, y1 as Float, x2 as Float, y2 as Float, Power as Float, Velocity as Float, nPasses as Integer > BOOLEAN
Adds a new line object to the current drawing using (x1, y1) as the top-left position and (x2, y2) as the bottom right position. ObjectName is assigned as the object name for the new line. The object will be created using the specified Power, Velocity and Mark Passes properties. All remaining object properties are set using the current default object properties as specified in the WinMark Pro application.
‘add new line from (-1, -1) to (1, 1) with 50% power, 100 inches per second marking speed and with 5 passes.
mh. AddLineEx “LineObject”, -1, -1, 1, 1, 50.0, 100.0, 5
Added AddPolyLineEx ActiveX method. Format the control as:
AddPolyLineEx < ObjectName as String, nPts as Integer, x as Single, bClosed as Boolean, Power as Float, Velocity as Float, nPasses as Integer > BOOLEAN
Adds a new polyline object to the current drawing where nPts is the number of X-Y coordinate pairs. x is the floating point starting address of the X-Y array.
If bClosed is True, then a line is drawn from the endpoint coordinate to the start point coordinate to close the polyline. When bClosed is False, the polyline ends at the endpoint coordinates.
ObjectName is assigned as the object name for the new line. The object will be created using the specified Power, Velocity and Mark Passes properties. All remaining object properties are set using the current default object properties as specified in the WinMark Pro application.
(see AddPolyLine in WinMark Pro’s ActiveX Control Help for descriptions and VB / C++ examples of XY arrays)
To use AddPolyLineEx with 26.7% power, 21.5 inches per second and 3 passes, the example for AddPolyLine would be modified to give:
mh.AddPolyLineEx "Polyline1", N + 1, Polyline(0).X, False, 26.7, 21.5, 3
New error codes for test mark download have been added to the GetMarkErrorCode ActiveX method:
10 Fiber link error. Head does not respond on entry to Custom Test Mark download method - Check that head is powered up, fiber optic cable connected, etc.
11 TESTMARK_MODE_CLEAR_ERROR. Cannot clear the current test mark mode.
12 TESTMARK_MODE_SET_ERROR. Cannot set the requested test mark mode.
13 TESTMARK_TRANSMIT_ERROR. Error during transmission of test mark to head.
14 TESTMARK_TOO_BIG. The test mark is too large for to fit in FH head memory.
Improved mark quality for color reduced bitmaps. Color reduction occurs when 8-bit or greater color bitmap images are imported into WinMark. The 8-bit image is converted into a 1-bit, monochrome, image suitable for laser marking. Color Reduction Methods include Bayer Dithering, Error Diffusion, and Halftone.
Added detailed “About” information to WinMark Launcher.
Added “Maintain Aspect Ratio” check box for Virtual Laser Marking images.
Changed spin control step sizes in Object Transformation and Virtual Laser Marking dialog boxes so that increments are 0.05 in. steps in inch units; 0.1 cm steps in centimeter units; and 1 mm steps in millimeter units of measure.
Wobble properties restored for circle/arc objects.
Added outline properties for filled polylines and arcs (similar to filled TrueType text).
Improved filling capability for irregular shapes.
Modified No-Cross functionality to work when Mark Count = 0 or > 1.
There is no limit on the number of custom date code formats. Previously the limit was 10 custom date code formats.
Custom Date Formats referenced on the object Automation tab are now saved in the mark file and in the creating computer’s System Registry, so that files with Custom Date Formats can be loaded on different computers without the ”undefined” format problem occurring. Custom date formats created using AssignDate in the Event Builder do NOT transfer with the mark file.
The Date Format Customization dialog has been changed slightly to accommodate additional custom formats.
Launcher window and Drawing Canvas now retain and display the last Auto Text Type value marked.
Some automated text and barcode captions are updated on the display when the object is selected or deselected. Dates, Times, and From Another Object sources are updated. Serial numbers are updated if Save Last Serial is Yes. Serial port and disk file text is not updated until the source is read during the mark sequence.
Grayscale marking now has the same behavior as the other conversion types so that black areas are marked and white areas are unmarked. Previously grayscale marking was inverted by default. When using build 4428 to mark files created with previous WinMark v4 builds, a dialog box reminds users to invert the pre-existing grayscale image to obtain the same mark results.
If Bitmap Scan Type is Continuous or if the Color Reduction Method is set to Grayscale (which uses Continuous scanning), then the product of marking Velocity and Resolution cannot exceed 33,000. In order to obtain an accurate mark, WinMark Pro will display a dialog box and then automatically reset Velocity to the maximum value possible at the specified Resolution.
Imported bitmap images are now resized according to the Resolution setting specified on the Tools/General Settings…/Object Defaults tab. Previously, WinMark Pro increased or decreased image size to correspond to a fixed bitmap resolution of 600 dpi.
ActiveX EraseDrawing method modified. EraseDrawing now only removes entities from the drawing leaving drawing properties unchanged.
ActiveX Reset method modified. Reset now erases all entities from the drawing and resets drawing properties to their default values as set under the Tools/General Settings…/Application Settings tab.
Right click on the installation executable (WinMark_Setup.exe) and choose Properties to view version information.
Automatic installation of Windows PCI device drivers.
During installation of version 4 software, the user can choose to save or overwrite pre-existing WinMark Pro Registry settings. Saving Registry settings prevents Custom Date Format definitions, shift codes, serial numbers, and other custom WinMark settings from being overwritten. Perform a “clean” installation by overwriting existing WinMark Pro Registry data.
Fixed issues when 2D barcode used in arrays.
Fixed memory resource leak issue with 2D barcodes.
Fixed problem were clockwise circles did not mark.
Fixed ragged edges on barcodes marked at low Resolution and low marking Velocity. In some instances, this may still occur due to incorrect Pline Start Delay and Pline End Delay values.
Fixed Stroke font bug seen when unprintable characters are used in radial text.
Fixed field transformations for arcs and ellipses.
Fixed problem when inverted barcodes are used in arrays.
Fixed issue with ActiveX AutoTestMark download.
Fixed European stroke font problem.
When setting up the Use Default option in AskUserInput from the Event Builder, WinMark Pro ignores the Default Text entry when From Default Text is chosen and instead uses the From Current Property Value.
We strongly recommend that all ActiveX control methods use inches as the unit of measure. Program your calling program to calculate the conversion to inches from other units of measure. Unpredictable object placement may result if the Show Units Type property in the mark file is set to millimeters or centimeters.
Linked objects in serialized arrays do not work. This is handled with a message and an error.
For best results when marking bitmap (raster) images, set a Resolution value that corresponds to 100–150% of the spot size generated by the selected focusing lens. For example, a 200mm lens with a spot size of 0.011” is capable of marking approximately 100 discrete dots per inch.
Generally, set Resolution equal to 200–300 when using an 80mm lens; 150–225 for a 125mm lens; 100–150 for a 200mm lens; and 50–75 when marking with a 370mm lens.
After changing Resolution and/or resizing the image, test mark the bitmap image. Use the Color Reduction Method property (Format tab) to change the color reduction algorithm as required. This change is performed on the original image, which is stored by WinMark during importation. Note that the screen display does not necessarily indicate the improved mark quality, so test marks are required.
When downloading a custom test mark file to the marking head, it is possible to setup output automation in the mark file so that one or more outputs can be Set/Cleared before or after the mark. This output automation can only be setup in the Event Builder (On Before Mark Session, On Before Mark Piece, On After Mark Piece, On After Mark Session) using the SetDigitalState event. No other events, including inputs, serialization, etc, are possible in a custom test mark file.
To use Chinese or Japanese languages with Windows 98 or NT4 operating systems, you must have a Windows 98/NT4 Japanese or Chinese version of the operating system installed on your computer.
To use Chinese or Japanese languages with Windows 2000 operating systems, you must load the correct Japanese or Chinese codepage and set it as the default from Regional Settings in the Control Panel.
When WinMark Pro v4.x is installed, your FH or Fenix Marking Head (firmware version 8 or above) can be upgraded to firmware version 20 directly from WinMark Pro. Follow the directions below to upgrade your Marking Head firmware to version 20.
1) Look for the file Update_20.asc in the WinMark program folder; usually this is C:\Program Files\WinMark but this may depend on the installation. If the file is already there skip to step 3, if not, you will need to download the firmware upgrade file – step 2. Note, if you are not sure which is the WinMark program older, right click the WinMark Pro icon on the desktop and select properties. Click “Find Target…”, this will take you to the correct folder.
2) There are two ways to download the firmware upgrade
file, select the one that suits you best.
From SYNRAD’s ftp site at ftp://apps.synrad.com/01w logon with the username “winmark” and the password “winmark01”. Select the folder FH_Firmware and copy the upgrade file, Update_20.asc to the C:\Program Files\WinMark folder.
From SYNRAD’s web-site at http://www.winmark.com/ and follow the instructions for downloading the latest firmware release. Note you will need to use your browser’s “SaveTarget As..” feature. Save the target in the C:\Program Files\WinMark folder.
3) Make sure that the Head is connected to the computer and is powered up.
4) Open WinMark Pro.
5) Check that the digital fiber optic link is OK by using WinMark’s Help\About Synrad WinMark…\Head Info button to check head status. The correct Head type, Lens, and Firmware version should be displayed. Continue the firmware update only if your Head Firmware version is 8 or above.
6) Close the Head Info dialog box.
7) Click the Update F/W button.
8) When the Marking Head Firmware Update dialog box opens, click OK to begin the firmware update.
9) When the Open dialog box appears, navigate to the WinMark installation directory (typically located in the C:\Program Files\WinMark folder).
10) Select Update_20asc and click the Open button.
11) WinMark Pro will download the file and indicate success. If there is a download error, try again. If there is still an error, use WinMark’s Help\About Synrad WinMark Pro…\Head Info button to see if the Head is still communicating. If the Head locks up and will not work, restart the original factory code by powering the head up while pressing the Test Mark pushbutton on the side of the Marking Head.
12) Power down the Head and power it back up to restart using the new version 20 firmware code. Open WinMark and click the Head Info button. It should now display the firmware version as 20.
If, for any reason, you need to reverse the firmware upgrade, click Help\About Synrad WinMark… . When the dialog box opens, click Update F/W and then click the Revert button. Follow the instructions on screen. If the firmware version is less than 20, revert to the factory-installed version by pressing and holding the Test Mark button while applying power to your Fenix or FH Marking Head. This will delete the firmware upgrade and restore the Marking Head’s original firmware version.
When serializing text strings containing lower case letters, the text string may shift up when lower case letters with descenders (g, j, p, q, s, y) are marked. This occurs because the Fixed To Position property defaults to "Center". Set the text Fixed To Position property to "Top Left", "Top Middle", or "Top Right" for best results.
Some Adobe Illustrator version 7.0 .AI or .EPS files may not import properly. If this occurs, save the file as a version 5.0/5.5 .AI or .EPS file and then re-import into WinMark Pro.
Some AutoDesk AutoCAD version 14 .DWG or .DXF files may not import properly. If this occurs, save the file as a version R12 .DWG or .DXF file and then re-import into WinMark Pro.
WinMark Pro’s File Import Filters do not support AutoCAD 2000 files formats. Choose “Save As” (DWG) or “Export” (DXF) and then choose to create the drawing as an R12 version.
On Windows 2000 and XP operating systems, a metafile containing multiple raster objects may import the last raster object in a “garbled” fashion. If this occurs, import vector and bitmap objects separately.
When Tracking, the Rising Edge Part Sense property must be set to Yes. Selecting No will cause erroneous “Line speed too fast – missed start” messages and subsequent missed marks.
On Fenix Laser Markers only, custom test marks may mark with a power setting different from the power specified. This can occur if a custom test mark is downloaded to the Marking Head and then marking is commanded (via Launcher, ActiveX, or the Drawing Editor) at a different power setting. The custom test mark is marked with the last commanded power value sent to the Head. To mark custom test marks at the correct power, remove and then re-apply power to the Marking Head.
Using ActiveX, Automation (Inputs/Outputs), and Tracking: When controlling Tracking using ActiveX control methods, do not place Input automation in the mark file. Instead, perform any input automation functions within the ActiveX control program. By doing this, your control program is in charge of pre-mark and post-mark automation; WinMark’s MarkDrawing control method only maintains control of the operating system long enough to control laser on/off commands during the actual marking process. Performing input automation within the mark file may prevent the ActiveX control program from regaining control of the operating system once the MarkDrawing command is called.
Using WinMark Pro or WinMark Launcher, Automation (Inputs/Outputs), and Tracking: When controlling Tracking using WinMark Pro or WinMark Launcher, do not use the Wait Digital Before Piece property on the Automation tab. This property is reserved for Tracker input functions (part sensor on IN0 and encoder inputs on IN1/IN2). Automation using Event Builder commands or other input/output commands on the Automation tab works as expected.
The Marking Head does not report input status (to Digital Scope, for example) when the Head is in Auto Tracking Custom Test Mark mode.
Very small objects (such as circles) may not display or mark precisely when imported into WinMark Pro from a CAD or illustration program. Best results are obtained by creating the objects directly in WinMark Pro. WinMark Pro is capable of displaying and marking objects drawn to four decimal place (one-ten thousandth of an inch) accuracy.
Text Height set on Format tab does not match Object Height shown in Object Transformations dialog box. For TrueType fonts, the Text Height value corresponds to the uppercase cap height of the font. The Object Transformations Object Height is the sum of the uppercase cap height plus the space above and below provided for ascenders and descenders. Note that Stroke font heights are variable (depending on the designer) and do not strictly conform to this description.
When using ActiveMark (ActiveX) control, objects are not automatically deselected after being selected (or added to the drawing). Use ClearSelection to deselect any selected objects.
When marking using ActiveMark (ActiveX) control, the Windows priority assigned to WinMark Pro and to the MarkDrawing method is high enough that only the Escape (ESC) key is recognized. Any key (except ESC) assigned as the abort key by the ConfigureAbort method is not recognized while marking.