======================================================================= SwiftView Windows Plug-in/IE ActiveX Version 8.0.2 Release Notes ======================================================================= November 5, 2005 SwiftView, Inc. Support: tech@swiftview.com or 800-720-0196x3, 971-223-2600x3 Note - these release notes now cover both the plug-in and the SwiftView C/IE ActiveX Control ("SAX"). The standard installation at http://www.swiftview.com installs the plug-in under Netscape and SAX under IE. For more information on either package see the SwiftView Plug-In Reference Manual at http://www.swiftview.com/tech/npextspec.txt or the SwiftView C/IE ActiveX Control Reference Manual at http://www.swiftview.com/tech/svaxref.txt. SwiftView Viewer and SwiftConvert contain open source, freely licensed software from the following sources: The FreeType team, www.freetype.org The Independent JPEG Group's cjpeg program ======================================================================= Supported configurations ======================================================================= Systems: Windows 2000 (all versions) (5.0.2195) Windows 2003 server (5.0.2195) Windows XP original, XP SP 1-3 (5.1.2600) Browsers: Mozilla Firefox 1.5 Microsoft Internet Explorer 5.00 (5.00.2314.1003) Microsoft Internet Explorer 5.00 (5.00.2614.3500) Microsoft Internet Explorer 5.01 (5.00.2919.800) Microsoft Internet Explorer 5.01 SP 1 (5.00.2919.6307) Microsoft Internet Explorer 5.0 ??? (5.00.3315.1000) Microsoft Internet Explorer 5.5 (5.50.4134.0600) Microsoft Internet Explorer 5.5 SP 1 (5.50.4522.1800) Microsoft Internet Explorer 5.5 SP 2 (5.50.4807.2300) Microsoft Internet Explorer 6.0 (6.0.2505.0000.main.010626.1514, 6.0.2600.0000) Microsoft Internet Explorer 6.0 SP 1 (6.0.2800.1106.xpclient.010817-1148) No longer supported: Windows 95osr2 (4.00.950B, 4.0.67109975) Windows 98 (4.10.1998, 4.10.67766222) Windows 98se (4.10.2222A, 4.10.67766446) Windows ME (4.90.73010104) Windows NT 4.0SP 4-SP 6b - Intel only (4.0.1381) Microsoft Internet Explorer 4.01 SP 2 (4.72.3612.1713) Netscape Communicator 4.73, 4.75, 4.76, 4.77, 4.79 ======================================================================= Plug-in Installation ======================================================================= The automatic installation at www.swiftview.com now installs SAX under IE and the plug-in under Netscape. For details on SAX installation see http://www.swiftview.com/tech/svaxref.txt. The SwiftView plug-in is available in one of the following installation packages: svinstall_p.exe -- executable installer for email delivery svinstall_p.jar svinstall_p_ics.jar -- in a Java Archive, for automated web-site download and install, all MIME types, or ICS-only. ***** Files installed with the plug-in ***** This file is installed under each browser's program directory: plugins\npsview.dll -- Plug-in shared library The following are installed under the SwiftView program directory (usually c:\Program Files\SwiftView): sview.exe -- SwiftView mime_sample.typ -- Example mime types file with default settings. mime.typ -- ICS-only mime types file, included only in the ICS-only installation. Only registers the .zhp suffix. svreadme.txt -- This file sview.tra -- Empty text translation file sview.str -- Sample (English) text translation file sview_.tra -- text translation files for various languages, e.g: sview_french.tra, sview_german.tra svinst.exe -- Install/deinstall program sview.inf -- Install/deinstall control file ***** PLEASE NOTE ************************************ You will have to set MIME types on your HTTP server to utilize this plug-in or SAX. See below. ****************************************************** A simple "one-click" installation is provided. If you are running Netscape Communicator 4.x or Internet Explorer 4.x, go to SwiftView's Download Page, http://www.swiftview.com/dload/dlmain.htm, and click the "one click install" option. The browser automatically downloads and installs the appropriate archive: Communicator installs the plug-in Java Archive, IE installs the Authenticode-signed SAX cabinet file. The plug-in is installed to run under both IE and Netscape, but SAX runs only under IE; if both plug-in and SAX are installed, IE runs SAX. For earlier browsers, download and execute svinstall_p.exe to install the plug-in. For more information about automated installation, see http://www.swiftview.com/howto/webhowto1.htm. The installer registers the default browser (and therefore SwiftView plug-in/SAX) to access files with SwiftView suffixes (see "Supported MIME types" below for a suffix list). This allows double-clicking or pressing the right mouse button on a file in Windows Explorer to display or print the file. Note that after the evaluation period ends, local file viewing requires licensing other than a basic web site license. Because of this, if another application is registered for the "Open" action, SwiftView is registered as extra "SwiftView" and "SwiftPrint" actions (right-click options), and the default actions are unchanged. Non-Standard Installations - The program registration for files can be overridden to view the file in a standalone SwiftView window, or removed entirely, by running the standalone SwiftView installed with the plug-in/SAX: c:\Program Files\SwiftView\sview -reg (run standalone SwiftView) c:\Program Files\SwiftView\sview -delreg (remove all registrations) Note that each time you click on a file in Explorer, a new SwiftView window is started. - Most Windows versions include a default .tif file viewer such as Imaging, Wang or Kodak. When SwiftView installs, it does not take over existing default applications, but adds SwiftView as an alternate application, available with the right mouse button on the file. If you wish to view .tif files with SwiftView by double-clicking on a .tif file, open Windows Explorer set the association manually by selecting View, Options, File Types, TIF Image Document, Edit, Actions: SwiftView, Set Default. This procedure varies slightly from OS to OS. - If you need to restrict the plug-in/SAX to only the application/vnd.SwiftView-ICS MIME type and .ics suffix for both local and web files, go to the page http://www.swiftview.com/dload/ics-only.htm. - If you need to restrict local file access to fewer MIME types, add standalone support for other types that SwiftView supports such as JPEG, or otherwise reconfigure local file access types or suffixes, you can do the following: 1. Run sview -delreg to remove the default SwiftView registration. 2. Copy the file: c:\Program Files\SwiftView\mime_sample.typ to the file c:\Program Files\SwiftView\mime.typ All the lines in the file that do not begin with '#' (comment) are concatenated together to make one configuration string. The format is: MIME:suffix,suffix...:description of mime type for file open dialog;MIME... 3. Either reinstall the plug-in/SAX, or run sview -reg depending on whether you want to use the plug-in/SAX under the default browser or standalone SwiftView to view local files. Note that you cannot add suffixes or MIME types to the plug-in in this manner; you can only add them to SAX or standalone. - If you would prefer to open a new window when viewing a file from Explorer, disable "Use DDE" in the Open action for the SwiftView file type(s) in Windows Explorer's View... Options... FileTypes... Open... Edit tabs. (This is the default if you are using standalone SwiftView). - Contact SwiftView if you wish to design your own installation package. Support is currently available to customize the final "click the back button" page, for example. Plug-in Installation Problems Should problems be encountered during installation, please review these notes before contacting SwiftView. - The default installation installs the plugin dll in the plugins directory under the following registry entry: HKEY_LOCAL_MACHINE\ SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Netscape.exe\Path It's data type is "REG_SZ", and it's value is the path to the browser's program directory. A non-standard browser installation may be missing it's path registry value, yet still function. Also, installing two versions of a browser, then deinstalling one version may remove this value. If neither registry value exists, the installer will look for the browser registered for .htm files, and set the path registry value for the appropriate browser to match. If no browser is registered, the user can enter an install directory, which must contain the "plugins" directory. If you want to run the SwiftView plug-in with another browser, contact SwiftView technical support. Reinstallation The plug-in installer automatically restarts any SwiftView plug-ins in any browser. Simply click on the back button to return to the previously viewed page. If SAX has already been run in this session of IE, IE must be shut down and restarted to run the new version of SAX. If your system is configured with "Active Desktop", you must reboot for this to occur. The installer notifies you if this is necessary. Plug-in Deinstallation All SwiftView packages, including the plug-in, can be removed from your system by either: - Clicking on "Start", "Settings", "Control Panel", "Add/Remove Programs", "SwiftView Products", "Add/Remove...", or - Downloading and running http://www.swiftview.com/product/current/svinstall_u.exe. ======================================================================= Supported MIME types ======================================================================= Plug-ins and (for non-OBJECT references) ActiveX controls are invoked based on the resolved MIME type of the document. The plug-in's MIME types are obtained from the plug-in DLL long before the plug-in itself is run by the browser. This means that once we create the plug-in at SwiftView, the MIME types are fixed. SAX mime types are configurable at install time. The default SwiftView MIME types are: Mime Type Description Filename Suffixes application/vnd.SwiftView-ICS SwiftView ics application/vnd.SwiftView-ZIP Zipped SwiftView zhp application/vnd.hp-PCL HP-pcl pcl, prn application/vnd.hp-HPGL HP-hpgl hpg, hpgl, hgl, hp, plt image/tiff tiff tif, tiff, 001 image/vnd.SwiftView-pcx PC-Paintbrush pcx, dcx image/vnd.SwiftView-cals Cals cal, ras The reasoning behind this selection of MIME types is: - A plug-in's registered types are fixed at compile time, and must be suitable for all users. - SwiftView does not register old, common "standard" MIME types like image/jpeg. These types are likely to appear on servers that lack SwiftView licensing, causing the 30 second no-license warning to be displayed. Also, existing users may already be comfortable with existing means of displaying the types and may not want to start using SwiftView for them. This choice minimizes interference with current installations. image/tiff is registered because most users want to use SwiftView with TIFF. However, when registering for local file access by suffix outside a browser (e.g. in Windows Explorer), "image/pcx" and "application/cals-1840" are used to remain consistent with standards. The actions are merged with other applications (press the right mouse button on a file in Explorer), so there is little interference with existing applications. - The HP types were only registered in March 1997, so there is little chance that they are in use with existing browsers. It's easy to get confused about where the mapping from file suffix to MIME type is actually done. In Netscape, filename suffixes are meaningful only when local file names are typed in the browser. The MIME type returned from your HTTP server determines which plug-in, control, or helper is used when documents come from your web site. However, servers also usually determine MIME types from the server file suffix. To make it even more confusing, Internet Explorer will sometimes work based on the file suffix if the server returns an "unknown" MIME type, or fail based on the file suffix even if the MIME type is correct. (see Internet Explorer-specific problems below). As a result you MUST do some work on your HTTP server to use the plug-in with any type other than TIFF. The easiest thing is to select all suffixes you wish to provide on the server and return them as "application/vnd.SwiftView-ICS". See below for server setup. Occasionally, some installations may make conflicting use of certain suffixes or MIME types. For such situations, a plug-in and SAX that support only application/vnd.SwiftView-ICS and the .ics suffix are sometimes available at http://www.swiftview.com/product/current/. Contact tech support if you require these but do not see them. Note that they also configure local file access as described in "Non-Standard Installations" above, by putting the line: application/vnd.SwiftView-ICS:svp,ics:SwiftView Command File in the file: c:\Program Files\SwiftView\mime.typ ======================================================================= HTTP Server Setup ======================================================================= Since the HP and SwiftView MIME types have only recently been registered, you must add MIME types to your HTTP server to use SwiftView with any type except tiff. Here are some example procedures for configuring servers: Netscape Communications Server: Edit the file: .../httpd-80/config/mime.types Add these lines as needed: type=application/vnd.SwiftView-ICS exts=ics type=application/vnd.SwiftView-ZIP exts=zhp type=application/vnd.hp-PCL exts=pcl,prn type=application/vnd.hp-HPGL exts=hpg,hpgl,hgl,hp,plt type=image/tiff exts=tif,tiff,001 type=image/vnd.SwiftView-pcx exts=pcx,dcx type=image/vnd.SwiftView-cals exts=cal,ras Apache: Edit the file: /etc/httpd/conf/mime.types or /opt/apache/conf/mime.types Add these lines as needed: application/vnd.SwiftView-ICS ics 001 application/vnd.SwiftView-ZIP zhp application/vnd.hp-PCL pcl prn application/vnd.hp-HPGL hpg hpgl hgl hp plt image/vnd.SwiftView-pcx pcx dcx image/vnd.SwiftView-cals cal ras Remove: application/vnd.swiftview-ics Microsoft Internet Information Server ******NOTE - IIS6 behaves much differently. See below******** Versions 2.0 and 3.0: Edit the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters\MimeMap Add as required: application/vnd.SwiftView-ics,ics,,: application/vnd.SwiftView-ics,001,,: application/vnd.SwiftView-zip,zhp,,: application/vnd.hp-PCL,pcl,,: application/vnd.hp-PCL,prn,,: application/vnd.hp-HPGL,hpg,,: application/vnd.hp-HPGL,hpgl,,: ... (http://www.swiftview.com/tech/npsviis.reg is a short script to load the SwiftView MIME types for IIS.) See the IIS documentation (http:///isadmin/htmldocs, chapter 10) for details on setting MIME types. Versions 4.0, 5.0, 6.0: There is no documented batch configuration method. To define a MIME type for a specific extension, follow these steps: You must open the Microsoft Management Console (MMC), e.g. Start, Programs, Windows NT 4.0 Option Pack, Microsoft Internet Information Server, Internet Service Manager (Internet Information Services Manager for IIS6). Right-click the local computer name, and then click Properties. Click MIME Types. Click New. In the Extension box, type the file name extension that you want (for example, .zhp). In the MIME Type box, type application/vnd.SwiftView. Apply the new settings. IIS now serves files with the extension that you added. In this example, IIS now serves files with the .zhp extension. .zhp application/vnd.SwiftView-ZIP IIS6.0 requires that you set the mime type on the SwiftView license file, or the file will not be read properly. To do this, in the IIS Manager, under the name of the local computer, under the Web Sites folder, click on the name of the website. On the right side you will see the list of files in the website root. Right click on npsview.lic and left click on properties. On the HTTP Headers tab, click on the MIME Types button. On the MIME Types window, click the "New" button, and create a type for .lic that has the type "text/plain". *****NOTE: Version 6.0: IIS 6.0 Does Not Serve Unknown MIME Types When you request a file from an IIS 6.0 Web server, and the file has a file name extension that is not a defined MIME type on the Web server, you receive the following error message: HTTP Error 404 - File or directory not found. Earlier versions of IIS include a wildcard character MIME mapping, which permits IIS to serve any file regardless of its extension. IIS 6.0 does not include this wildcard character MIME mapping and does not serve any type of extension that is not defined at the MimeMap node in the IIS metabase. WARNING: If you edit the metabase incorrectly, you can cause serious problems that may require you to reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk. *********NOTE: Always back up the metabase before you edit it. If you want to serve all files regardless of the file name extension (for example, if you cannot predict all files that will be served), check Microsoft's website for that information. They recommend doing that only for troubleshooting as a temporary solution. Note that restarting IIS from it's manager interface or from "World Wide Web Publishing Service" in the NT Service Manager does not reliably reconfigure the MIME types - a reboot is the only reliable way. Note: if you access your server from a browser, then add the SwiftView MIME types, hitting the browser refresh/reload button does not always reliably update the new MIME type. If problems persist, empty the browser's file cache; if that fails, restart the browser. Any number of extensions can be added for files to be viewed by SwiftView. Other examples include .jpg, .cal, .pcx, .plt. Note that SwiftView does not use extensions or MIME types, but looks inside files for actual content. The result is that any file supported by SwiftView can be returned as type "application/vnd.SwiftView-ICS". However, using vnd.hp-HPGL and vnd.hp-PCL for these formats may make your web site compatible with other software in the future. You can install a file "npsview.ics" at the root of your http: or ftp: server containing ICS commands that configure SwiftView for your site. See the SwiftView Plug-In Reference Manual for details. ======================================================================= Licensing ======================================================================= The SwiftView plug-in/SAX are licensed software. Licensing is accomplished in one of several ways: - A LAN license, for installation of SwiftView on a LAN server - A client-side license, for integration of the SwiftView plug-in into a commercial software product. - A web license, installed in the root directory of the web server containing the SwiftView documents - SwiftStamp, which embeds a license in the document file. Without one of these license files, the plug-in/SAX functions after a 30 second delay, enforced by a non-dismisssable dialog. The intent is to induce business users to purchase web site or LAN licenses but not be unreasonable for home users to "wait it out". A license may be purchased by contacting: email: sales@swiftview.com voice: 971-223-2600 fax: 971-223-2601 For more information visit http://www.swiftview.com/buy1.htm. We can email you a license file within one business day of reciept of a purchase order. You must supply your company name and address and which type of license. For the web license you must give the name(s) of the server host, as accessed in URL's. For the LAN license you must give the department name or other general LAN identification. For the CDROM, you must give the filesystem label on the CDROM. In all cases, say whether each license is for users running Windows, Unix, or both. If there is a valid SwiftView LAN or client-side license in the file specified by the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\SwiftView\lanlicense (version 5.3 or later), else the "lanlicense" parameter in the Windows default sview.ini file, else "sview.lic" in the SwiftView program directory, else any directory in the user's PATH, the plug-in/SAX is fully licensed for use with any server or file. The license is checked at the first plug-in/SAX instance in a browser session. LAN licenses may not be in the c:\ filesystem; they are intended to be installed with the software on a LAN server. See http://swiftview/tech/techfaq.htm#LanLicense for details and installation procedures. Otherwise, each time a non-ICS document or document page is specified, via SRC parameter, ldoc, or onpage command, the following licenses are checked: - SwiftStamp in the file. - web license, if the file is an http: URL, else - file was previously downloaded from a licensed web site. The web license is obtained from the file: http[s]:///npsview.lic where the URL to the document begins with "http[s]:///" is checked for a valid license for . (Note that the usual browser file caching applies to web license files.) ======================================================================= User Interface Configuration ======================================================================= The SwiftView plug-in/SAX provides extensive mechanisms to customize the user interface. See the SwiftView Plug-In Reference Manual for details. Translation to other languages All SwiftView packages support translation of user-visible text strings for Western European languages. See the SwiftView Plug-In Reference Manual for details. ======================================================================= Known problems ======================================================================= Scrollbars and buttons are not reset to default between plug-ins. Added buttons accumulate across instances as a result. Netscape sometimes crashes on the next plug-in access after a plug-in reinstall if a different plug-in version was previously installed. IE has a similar problem with SAX. Embeding plug-ins in frames is unreliable, with a variety of intermittent and repeatable failures with different browsers. Use of the EMBED tag rather than frames is strongly recommmended. Use of the EMBED tag within a frame rather than a simple full-page instance will alleviate most of the resize bugs in Netscape. However, Netscape sometimes crashes when rapidly resizing frames containing an EMBED plugin using ldoc http: commands. Any print job being processed by SwiftView (i.e. the printing dialog is still up) will be cancelled by leaving the plug-in page. If an ICS file has an error, the error message shows the cached filename, not the URL. Hit F8 to see both names. If SVIEW.EXE is killed, you must leave and return to the HTML page containing the SwiftView document(s) to restore operation. Occasionally the Win95 hourglass cursor fails to appear when it should. No plug-in download and install menu is displayed when an HTML page containing a HIDDEN plug-in is accessed and the plug-in is not installed. Printing a page with an embedded plug-in prints only the surrounding html page. Print dialogs remain on top when other windows are activated. ftp:// access of a SwiftView file crashes the browser if npsview.ics or npsview.lic is not installed. Under IE the plug-in cannot access ftp://user@hostname, only anonymous ftp://hostname where no password is required. ActiveX-specific problems A Mouse click in an OBJECT or EMBED may not cause the control to get all of the keys. Usually all keys go to the OBJECT initially, but after a click in the HTML area, clicking in the SwiftView object does not get Home, End, PageUp/Down, arrows, or ctrl-f. ctrl-f gets the IE find dialog instead. Other similar problems exist in various IE versions. Sometimes it stops getting keys after a few are typed, e.g. "Page Up". ctrl-C and sometimes alt-Insert may not work, where alt-C or a plain "C" does work. Key focus is not directed to the clicked instance of multiple SwiftView OBJECTs on a page. Netscape-specific problems Netscape prevents use of certain standard control and function keys, so five SwiftView commands (noted in the help dialog) are accessable in the plug-in via other non-standard keys. After a SwiftView dialog is dismissed, keys are sent to the sview executable, so these control and function keys will start working under Netscape, and "h" gets the standalone help dialog. If you flush the Netscape cache while a plug-in page is up, Netscape instantiates a bogus plug-in from an old cached file that has been removed. Then sview hangs with an error message up. Fixed in Communicator 4.04. Files accessed via secure http may fail to display. Fixed in Communicator 4.04. Navigator 3.x does not handle "file:" URL's correctly unless all three slashes are given, e.g. "file:///l:/qa/tiff.001". Simply giving a file path in an HTML page, e.g. "l:/qa/tiff.001" also fails, though it works when hand-entered. (not fixed in 4.04). Communicator 4 on NT or Win95 will load standalone SwiftView as a helper (after popping a security dialog) instead of loading the plugin for a file:///*.001 URL if the registry contains a file extension entry for .001. This entry consists of, e.g.: key: HKEY_CLASSES_ROOT\.001 value: "[Default]"="001_auto_file" (maps to the following key:) key: HKEY_CLASSES_ROOT\001_auto_file\shell\open\command value: "[Default]"="c:\windows\sview.exe "%1"" Breaking this arrangement in any way causes netscape to pop the "Unknown File Type" dialog. Removing the HKEY_CLASSES_ROOT\.001 key, or adding key: HKEY_CLASSES_ROOT\.001 value: "Content Type"="image/tiff" clears up the problem. Similar entries for other suffixes have not been seen to cause the problem, but do not depend on this. Note that HKEY_LOCAL_MACHINE\SOFTWARE\Classes is a mirror of HKEY_CLASSES_ROOT - only edit HKEY_CLASSES_ROOT. Note also that entries won't appear in the Windows Explorer View-Options-File menu if there is no "[Default]" value for the HKEY_CLASSES_ROOT\001_auto_file key. This value is also what IE displays in it's File:Properties menu Type field. Netscape may hang for 15 seconds if a file on the server such as npsview.ics is an empty file. Microsoft Internet Explorer-specific problems IE may fail to download the file generated from a POST request for a SwiftView MIME type. Problem is exhibited with both plug-in and SAX; with the plug-in, the probability of failure increases from near 0% to near 100% with file size. With SAX, IE fails in a variety of ways, depending on SwiftView and IE versions, sometimes repeatably, sometimes erratically. With IE 5.5, some URL's will work, others won't. IE may request multiple transfers for GET or POST queries, slowing the file transfer. Printing via Internet Explorer File menu or print button does not work properly (various failure modes). Printing via control-P doesn't work with an EMBED/OBJECT SwiftView instance. Use the SwiftView print button. The File...Save As IE menu item is greyed out when viewing a page with plug-in or ActiveX. You can right-click on a link to the page to "Save Target As". Unless all SwiftView MIME types are registered at the server, Internet Explorer maps types according to the control's suffix rules in an unreliable fashion. Often one control or server-defined suffix for a MIME type will work, while other suffixes for the same MIME type will fail. Using a separate MIME type for each suffix can resolve some problems. If you forget to set the server MIME types, you must clear the Internet Explorer file cache, shut down Internet Explorer, remove all SwiftView MIME registry entries in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Plugins\Extension HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Plugins\MIME HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type HKEY_CLASSES_ROOT\MIME\Database\Content Type (link to above location) set the SwiftView MIME types in the server, and restart Internet Explorer. (HKEY_LOCAL_MACHINE\SOFTWARE\Classes\* is always identical to HKEY_CLASSES_ROOT\*). Unless the URL ends in one of the suffixes registered by the Active X control, Internet Explorer may erratically fail to start the control, even though the MIME type matches the control's MIME type list. When it fails, IE displays a small red x icon for a full-page control, or an "unknown object" icon (three colored shapes) for an EMBED. Note that this also applies to cgi script files; they should have a SwiftView suffix somewhere in the URL, e.g.: http://myserv/cgi_bin/spsrv?file=file.txt&suff=.zhp Note that the suffix must be the end; this doesn't always work:
File to display (POST)
IE 4.0 does not work with a HIDDEN EMBED. You are forced to set WIDTH or HEIGHT to zero and AUTOSTART true. IE 4.0 sometimes pops it's window in front of the SwiftView helper-mode window at plug-in startup. Problems with embedded views The Netscape reload/Internet Explorer refresh buttons do not cause cached EMBED/OBJECT SRC plug-in files, http: files referenced in a document ICS file with onpage, npsview.lic, or npsview.ics to be reloaded. To get all files updated, you must also press the F5 key. Under some circumstances, Internet Explorer starts plug-ins before it draws the HTML, then sends extraneous redraws to the plug-in when it draws the HTML. It can happen intermittently with a single plug-in instance, repeatably with 5 instances. It can also redraw the html several times while drawing the plug-ins. Embedded (in-context) printing is not implemented. SwiftView can print the contents of it's own embedded windows using it's own print button, but the HTML page as a whole including plug=ins cannot be printed. The drawing window border and/or scrollbars can fail to draw on a zoom. Internet Explorer causes the plug-in to redraw every time it loses or gains keyboard focus. When scrolling an HTML page with an embedded plug-in or SAX control, SwiftView may draw part of the drawing over the HTML area. SAX may also have part of it's drawing clipped out. ======================================================================= Feature/bug fix history ======================================================================= These notes describe features and bug fixes that apply only to the plug-in and SAX, not standalone SwiftView. They augment the regular standalone SwiftView release notes, which almost always apply to the plug-in and SAX as well. ======================================================================= ***** Problems fixed/new features in 4.2.3 ***** ======================================================================= Files accessed as UNC names (\\host\drive\path) failed. ICS-only plug-in now registers only ICS suffixes for local file access. sview license dialog could appear improperly - prevent from killing the sview init commands. URL's with :portnumber failed. Page dialog could come up off-screen, or in wierd locations. Position page dialog relative to cursor and keep it on-screen. Stop white flashing on resize. Save dialog hides it's own file selection dialog. ======================================================================= ***** Problems fixed/new features in 4.2.5 ***** ======================================================================= Resize now works under IE. Plug-in no longer can leave orphaned sview.exe processes. With this release, sview.exe is always terminated on plug-in instance termination. Toolbar property dialog could not reconfigure embedded gui. The ICS system command was not disabled (security risk). Add LiveConnect support. ======================================================================= ***** Problems fixed/new features in 5.0 ***** ======================================================================= The URL "#fragment" syntax is now supported - append "#" and any ICS commands to the URL. Imap mail attachments now work. Silent install now reports no error if unable to install for the non-default browser. Added -e "really silent" option to log errors to stderr instead of popping a dialog. DOS box during install is now suppressed. sview.exe is now installed in the Windows directory, for all to share. ======================================================================= ***** Problems fixed/new features in 5.0.1 ***** ======================================================================= Non-ICS files can occasionally send bad ICS commands to sview. Security restriction should not be applied to commands from GUI. ======================================================================= ***** Problems fixed/new features in 5.0.2 ***** ======================================================================= Force initial keyboard focus to plug-in. Empty Web npsview.ics file caused a crash. ======================================================================= ***** Problems fixed/new features in 5.1 ***** ======================================================================= Correct handling of non-existent http: files. Fix problems with browse command (hotspots). See general release notes for the many new features. ======================================================================= ***** Problems fixed/new features in 5.1.1 ***** ======================================================================= Add corporate SwiftStamp licenses. SAX: Add property, method, and callback event support. SAX: Fix crash problems under VB. SAX or plugin reload did not work with https:. ======================================================================= ***** Problems fixed/new features in 5.2 ***** ======================================================================= New installers, much cleaner, with automated deinstall. Plug-in and SAX are now dynamically linked to mfc42.dll and msvcrt.dll, saving download size. The .exe install package remains statically linked for installation on systems not connected to the Internet. http: file access now works with HTTP Basic Authentication (username and password entry). The SwiftViewPlugin.class file for LiveConnect is now installed with a separate .jar file. The "Bird" logo and all icons are now replacable in a custom install package - contact SwiftView, Inc. for details. The 30-second no-license dialog can be cancelled, rather than forcing the user to wait 30 seconds to quit using the control. A number of unusual crash bugs are fixed. Callback strings are now reliably sent to applications (e.g. in LiveConnect). ======================================================================= ***** Problems fixed/new features in 5.3 ***** ======================================================================= IE 5.5 (5.50.4134.0600) may fail after SAX is invoked. Restore plug-in installing for IE as well as Netscape. ======================================================================= ***** Problems fixed/new features in 5.4.1 ***** ======================================================================= SAX may crash on some systems running IE 5.5 SP 1 on Win NT and 2000. ======================================================================= ***** Problems fixed/new features in 6.0 ***** ======================================================================= Netscape sometimes crashes when resizing frames containing an EMBED plugin using ldoc http: commands, or otherwise doing multiple file loads via http(s). It can still crash, but only when resized multiple times in rapid succession. SwiftView plugin, ActiveX, and SwiftInside could occasionally hang on initial document display. The tool bar showed, but the document did not. This problem was fixed long ago in plugin and ActiveX, but the fix was broken at version 5.5. B1519: wininet under ActiveX sometimes hung for file sizes near but not exactly multiples of 1K. ======================================================================= ***** Problems fixed/new features in 7.0 ***** ======================================================================= Errors encountered before the ActiveX control was fully initialized (e.g. license errors) could crash the application.