[ad_1]
There are 2 known bugs in Leopardmark and Prolase 7 Laser Marking Software. Leopardmark is the standard software offering in Jimani’s Low Cost Fiber Laser Marking Systems and is a variation of American Laserware’s Prolase 7 Laser marking Software.
1. Preview Box with text objects: When the internal red guide laser is activated, the Preview tool on the Standard Tool Bar is intended to place a bounding box around the individual objects to be marked. That Preview Box does not accurately display the marking location if a text object has more than one line of text. If a text object has more than one line of text, the Preview bounding box displays the correct size of a multi line text object but the bottom of the bounding box is always at the bottom of the first line of text and the rest of the bounding box is drawn above that first line of text. The only solution that I am aware of is to make each line of text a separate marking object and locate it correctly with respect to the other line(s) of text. Those lines of text can then be made into a “group” and that group can be Centered About The Origin in the Group Properties dialog box. Then, when the Preview command is selected a separate bounding box will be drawn around each of the individual text objects.
2. Internal laser pointer turns off when any object from the Stock Objects tool bar is selected: If the internal red guide laser has been turned on from the Mark Control dialog box, it will immediately turn off if anything is selected from the Stock Objects tool bar. Even though the guide laser has turned off, it still shows as being on in the Mark Control dialog box. Turning the guide laser OFF and the ON again re-enables it.
Since both Leopardmark and Prolase 7 are frozen, these bugs will not be corrected. The “Preview Box text objects bug” has been corrected in Prolase 10 but the “Internal laser pointer turning off” bug exists in Prolase 10 but was unknown until I notified American Laserware of it. Keith Cudebec, the founder of American Laserware, assures me that this bug will be corrected in Prolase 10.
[ad_2]
Source link