SwiftReprint Release Notes Version 2.5.1 October 14, 2004 SwiftReprint News We have been delighted with the rapid acceptance of our SwiftReprint product. SwiftReprint continues to improve in response to your feedback. Please contact the SwiftView Tools product manager, Glenn Widener, glennw@swiftview.com if you have any specific feature requests. The 2.5.1 release of SwiftReprint adds major new features: - Instantly compose an email message with your document pre-attached. - Easier-to-use markup with menu shortcuts and "Keep Tool" mode. The newest release of SwiftView, version 7.1, includes several bugfixes that affect SwiftReprint and is recommended for all SwiftReprint users. The previous release of SwiftView, version 7.0.1, enabled "Pages On Demand" PCL page caching from a file under SwiftReprint. This makes repeated accesses of the same PCL file in SwiftReprint essentially instantaneous. For example, you can now direct print the first few pages of a large PCL file quickly, without waiting for page counting to complete. Then, if you leave SwiftView running until page counting completes, you can subsequently extract any range of pages (e.g. to split the file across several printers or reprint the end of the file), almost instantly - even with files with a million pages! Installation SwiftReprint 2.5.1 or later requires the SwiftView Viewer ActiveX control 7.1 or later. Install it from http://www.swiftview.com/download.htm. SwiftReprint 2.5.1 is compatible with SwiftPublish 2.5.1 or later. Minimum supported systems: NT4 SP6, win98 Second Edition, or Windows 2000+/XP, all with IE5 or later installed. Licensing When the demo period expires, one month after installation, you must obtain a SwiftReprint license. The following licenses are available: - Single-user workstation, application server, LAN or WAN. SwiftReprint is a separately licensed product from the SwiftView viewer, using the same licensing files as the SwiftView viewer. - SwiftStamp. SwiftReprint can be used with files previously SwiftStamped using SwiftPublish or SwiftReprint. Contact SwiftView sales for information on purchasing this optional feature with the SwiftStamp Batch utility. - OEM licensing to embed in an application. A customer-specific license string is passed on the SwiftReprint program command line. It is recommended for security reasons that this license string not be visible to end users, i.e. that it be embedded in an executable program. SwiftReprint Known Bugs Complete release notes for SwiftReprint include the release notes for SwiftView 7.1. The following are the known problems and desired additional features in SwiftReprint itself: F3169: initialize browse directory per currently displayed path. Open box should startup in the directory currently shown in the file box. B3179: save to file button refresh issues: - interface counter intuitive - path and filename must be re-entered to re-enable the button - no file overwrite prompt B3126: SwiftReprint and SwiftPublish are licensed the same. If you install a licensed OEM version of SwiftPublish or SwiftReprint, you cannot install a version of either product that is not licensed for the same OEM, as they share a common spack.dll and license strings. B3076: Each reinstall adds a markup deinstall entry. Add/Remove Programs shows multiple "SwiftView Markup" installed programs. Easier to remove them if you first delete all but one c:\program files\swiftview\ST6UNIST.nnn. F3077: Add markup disable button. Add a button to the Review SwiftView execution from SwiftReprint to view/not view markup. F3078: Put original page count in stamp. Record the original page count in the initial stamp from SwiftReprint. (i.e. only if original file is not stamped.) B3087: From and To fields: Make the default page range 1 - last. B3088: Extract Pages: grey-out this area if the Original File is one page. If the original file is one page in length, then grey-out the "Extract Pages" area. We had also talked about locking out access to the Reprint dialog while Markup was up, but I dissed that idea. B3097: SwiftReprint License field: The license string should be encrypted. This is a known SwiftPublish bug. Once you hit ok, then the encrypted license string should be reflected in the options area immediately. At this point, the license string field will reflect the encrypted registry string after the program is completely restarted. B3100: Stamping: stamping should occur before review. B3113: Can't recover from errors during extraction. If SwiftView errors during page extraction, Reprint doesn't notice and will have an empty extracted file until input settings are changed. F3167: Request: Help message when Extracted Pages is greyed-out. I noticed that the help message for Extracted Pages might be useful when the Extracted Pages is greyed-out. B3266: Calculation of text width for sticky notes is inaccurate. SwiftView Problems that affect SwiftReprint The following are a few SwiftView bugs that are particularly noticable from SwiftReprint. SwiftView markups except for arrows draw over themselves during XOR feedback, causing ragged edges. If you do a lot of resizing of a graphic during creation, eventually the dynamic feedback stops working correctly until you page down and back. Logged sview error: "Ran out of display list pages". If the SwiftView UI is set to default to text selection, not zoom, a highlight text note's message doesn't display on a click without pressing the alt key. SwiftView doesn't rescale properly, e.g. on draw all after an undo of a markup outside the page - seems to remember old bounding box after markup is removed. White text background isn't quite as white as doc background. B3165: commands to disable markup display only last until page is changed. This affects the "hide markups" button in SwiftReprint review. Bugs Fixed/Features Added in 2.5.1 Release B3626: wierd highlighting when paging. Highlight text operations would turn funny colors when paging out and back. B3638: new stamp metadata not visible in standalone SwiftView. Load a stamped original file, extract the entire file (e.g. range 1-999), zip and restamp. The original stamp remains on the file inside the zip, so standalone (but not controls) sees the old stamp instead of the new one. B3625: totally haywire markup coordinates. Happens rarely, though should be often... SwiftView B#3624, fixed in 7.1. B3577: print to default and page extraction can fail. Neither operation was sending "", so they wouldn't complete (extraction not a problem until sv 7.0.3) B3580: page extraction fails in the presence of a lan license. If a lan/client license was found that did not enable batch direct print range of pages, SwiftReprint could not extract. Fixed in SwiftView 7.1. B3588: page extraction performance improvement. Actually, this is an enhancement (F#3300) in SwiftView 7.0.1: allow extracting ranges before counting is complete. 2.5.1 is the first Reprint release after 7.0.1. B3610: problems saving attribute settings. Attribute settings that exist when a new file is opened aren't getting saved to the file. Also, attributes set without creating an entity aren't saved. Example: Set attribute+draw+undo+save+resetting same attribute+save: new attribute not written to file. B3536: quiet markup installer. Eliminate the silly install button from the markup installer running under the Reprint installer - it's just confusing. F3535: Add an email button. SwiftReprint now can start the user's mail client with the output file preattached and a decent message body with SwiftView installation instructions. Starts the default mail client - tested with Outlook, Mozilla, Netscape, and Eudora. F3438: Keep current Markup operation. If you choose a type of markup, lets say free hand, you draw a line, and then it resets. You have to go select the type of markup you want again. This is really annoying, lets say I want to draw 4 lines, I have to select line 4 times. Keeping the current tool is now an optional feature, on by default. Only for simple commands, won't work for commands that require text input prior to mouse selection. B3447: minor license handling bugs. apparent bugs similar to B3445 in SwiftPublish: Demo period/timebomb/LAN Licenses not being correctly reported in gui info area. LAN license not checked by timebombed version. Full license string failed to initially enable options after entering license, clicking OK, and redisplay of options dialog. GUI-only license string fails to disable full license in registry. F3268: Markup editor needs shortcuts. The markup editor needs easier ways to add multiple markups - add alt key menu shortcuts. B3267: Cannot load an ICS file not created by the markup editor. The markup editor only handles files it created, and may do wierd things on other ICS files. B3265: random selection of text on adding markup. After a highlight text operation, a select text operation on the same region can get triggered (visible because it gets select highlighting.) Sometimes drawing a graphic after adding text causes the text to be selected. B3264: No error message appears when trying to save to a read-only directory. Silently fails. B3181: Sticky Link markup broken. -can apply it but can't get it to invoke browser B3094: The size of the SwiftMarkup window should be maintained like it is in SwiftView and should start larger. SwiftMarkup starts at a smaller size than SwiftView. It should start at the same size as SwiftView. It should also maintain any size adjustments - shared with SwiftView? B3090: Review: Ensure that only one instance of SwiftView is running. B3091: Markup: Ensure that only one instance of SwiftMarkup is running. Bugs Fixed In 2.4.0.1 Release Note - 2.4.0.1 was a quick patch release of markup only, and still identifies itself as 2.4. F3239: Save user attribute settings in registry. Instead of initializing them from the ICS file's last settings. B3119: undo/undo all/remove all not working. RemoveAll, do, undo, redo, undo all, do - eventually stuff comes back, both the original file stuff and the current edits. B3180: File Menu, Save button does not save changes properly. -must be clicked to re-enable remove all markups -markup colors not constant after save or reloading -previously removed markups may reappear upon save -only Save to File seems to save permanent changes