The following text provides information about specific issues that you may encounter with the DevPack Preview Release of eSuite Applets and Sample Applications:
The notes are divided into the following sections:
Section 2: Common Applet Issues
Section 3: Applet-Specific Issues
Section 4: Template Builder Issues
Section 5: Sample Application Issues
Section 7: International Issues
Section 8: License Information
The eSuite DevPack Preview is for evaluation purposes only. Applet API methods and properties are not complete, and may change substantially between DevPack Preview and DevPack Release 1.0. As a result, applications that you create using Preview-based API may not work in eSuite DevPack Release 1.0.
For issues not covered within the scope of this document, Lotus has provided an unsupported discussion forum where you can read information from, post questions to, and submit feedback to other DevPack Preview users. This forum can be reached from the eSuite DevPack Preview home page.
**********************************************************************
This section contains general information specific to the DevPack Preview Release of eSuite Applets and Sample Applications.
Note: Recommended browser versions
It is recommended that you use this release of eSuite with Internet Explorer Version 4.01 or Netscape Version 4.04. See the Browser Issues section of these notes for more information.
Note: Selecting the correct system display settings.
You must configure your system to run with more than 256 colors for both Internet Explorer and Netscape when running eSuite.
Note: Printing with eSuite applets.
Print jobs may not print (the job queues but does not print or does not even queue) when running under Internet Explorer 4.0 or Netscape 4.04 This depends on the particular combination of printer and print driver that is being used. Print jobs sent to an HP III or IV using the appropriate print driver will generally print. Jobs sent to other combinations of printers/drivers may or may not print.
Note: DevPack Preview release version of the InfoBus is incompatible with public versions.
The DevPack Preview release was built with an early version of the InfoBus that is not compatible with any of the public releases. This will be fixed in the final release of DevPack 1.0.
**********************************************************************
SECTION 2: COMMON APPLET ISSUES
This section describes issues common to all applets:
Issue: Difficulty is encountered when determining where the keyboard focus is when using InfoCenter panels (dialogs).
Workaround: When using popup panels in the InfoCenter, click with the mouse in each control you wish to activate. When completing a command, use the mouse to click the OK button (or Cancel button, as appropriate).
Issue: Text may be truncated on the InfoCenter panels if your system display Font Size is set to Large Fonts.
Workaround: Check you Settings Control Panel Display settings Font Size. Change the font size to small fonts.
**********************************************************************
SECTION 3: APPLET-SPECIFIC ISSUES
This section describes issues specific to the following applets:
Issue: Attempting to programmatically delete an object fails with certain function calls. The following Wordprocessor Object model function calls do not appear to delete the object that they are intended to delete.
Issue: The insertPageNumber API function call does not appear to set any format other than decimal.
Workaround: Use the decimal format when using this function.
Issue: Links created with insertLink do not appear to function correctly in the user interface.
Issue: Editing hyperlinks with the WP applet creates problems. The wordprocessor allows a link to easily be created to a region of text or an image by selecting insert/link and then entering a reference path for a URL or bookmark in the InfoCenter panel. It is however, not entirely intuitive from the user interface how to edit or remove a link that has been created.
Workaround: Editing and updating of existing links and targets can be performed by arrowing the cursor (insertion point) into the link area and then selecting insert/link from the menu. The URL or bookmark reference can be updated within the InfoCenter panel in which it appears.
Issue: Connecting connected cells within a table fails when cells do not lie within first table column. An attempt to connect a group of cells within a table, followed by a subsequent attempt to reselect that connected cell within another region of cells and connect that region will be unsuccessful if the original group of connected cells did not include cells from the first table column.
Workaround: Editing and updating of existing links and targets can be performed by arrowing the cursor (insertion point) into the link area and then selecting insert/link from the menu. The URL or bookmark reference can be updated within the InfoCenter panel in which it appears.
Issue: Inserting a graphic into a WP doc opened using the HTTP protocol fails when using a file path. The WP applet attempts to make assumptions regarding file I/O operations pertaining to how a document was opened in the first place. If HTTP is used as the file protocol for opening a document within the WP applet, then the applet will append an image path such as X:\Server\directory\image.gif to the http extension when an attempt is made to insert a graphic, creating an invalid URL location. Any attempt to insert a graphic using standard file open protocol will be unsuccessful.
Workaround: If using HTTP to open a word processing document within a browser, an image must be inserted using the same http protocol. If using standard file open to open a word processing document within a browser, you can use either HTTP or file open protocol as the path for a graphic.
Issue: Copying and pasting of text within a table works incorrectly within Netscape 4.04 and IE 4.01. If, after creating a table and entering text into its respective cells, the table is highlighted, and the contents are pasted to a line outside of and below the table, the text pastes incorrectly, with the contents in the first column pasted correctly, and all other data aligned with the right margin of the document.
Issue: Quit menu selection is not functional within a browser. Selection of the document\quit items within the WP InfoCenter does not function when the applet is brought up within a browser such as Netscape 4.04 or Internet Explorer 4.01.
Workaround: Select File-Close on the browser menu in order to exit.
Issue: Applying text attributes produces unexpected results with certain languages such as Japanese, Chinese, and Korean. If an attribute is applied when the insertion cursor rests in the middle of a word, the attribute is applied to the entire word. If the attribute is applied between words, such as, at a space character, the attribute is applied from that point on. This is a logical set of rules when applied to the English language where the standard delimiter between words is the space character. The Eastern languages such as Japanese and Chinese are different in that words are not necessarily delimited using the space character, and thus when an attempt is made to apply an attribute to a single character, the attribute is instead applied to the entire body of characters on either side of the character not separated by a recognizable delimiter symbol. The setting of attributes therefore yields unexpected results in those languages, sometimes changing the attribute for an entire page because of the differing language syntax.
Issue: Value entered into margin field is rounded to nearest tenths decimal place. Although you can enter a value with a decimal precision of two places or more, the field will round to the nearest tenths place. For example, entering a value of 1.55 will round to 1.6.
Issue: The Data Source panel is currently display-only.
Workaround: If you open this panel, you must reload it from the Browser and restart the chart to close it.
Issue: Scale Type option for the Y-axis is not implemented.
Workaround: To set the scale type use the yAxisScaleType HTML parameter.
Issue: Problems occur setting the Y-axis maximum and minimum values.
Workaround: To set the Y-axis maximum and minimum values, either use the user interface value spinner or edit the value manually. Do not use both.
Issue: Series colors occasionally do not match the Legend color swatch (primarily with colors in the yellow range).
Issue: Chart components cannot be changed via the InfoCenter.
Workaround: Changes to axes titles and series markers currently must be made via the HTML parameters in the source page. The chart note must be set via HTML parameters before it is visible on the page and can be edited via the InfoCenter.
Issue: Problems occur setting negative values for the X-axis and Y-axis.
Workaround: To set negative values use the following HTML parameters : XAxisScaleMax, XAxisScaleMin, XAxisScaleMajor, XAxisScaleMinor, YAxisScaleMax, YAxisScaleMin, YAxisScaleMajor, YAxisScaleMinor.
Issue: Problems occur setting the Y-axis scale greater than 100.
Workaround: To set the limits for Y axis scale greater than 100 use the following HTML parameters : YAxisScaleMax and YAxisScaleMin .
Issue: Area series in Radar extends beyond plot.
Issue: EdgeBackground color for plot does not work.
Issue: Printing problems occur with Chart applet.
Workaround: To print a chart, use the Print function of your browser.
Issue: Problems occur entering Axis Titles and FootNote text.
Workaround: Use available HTML PARAM tags or API settings to define these elements and assign non-default values.
Issue: Transparent series displays as filled (color) in legend.
Issue: X Axis labels collide when displaying
Workaround: Stacked 2D and 3D Area charts do not render correctly. To ensure accurate data plotting, use unstacked area charts.
SHEET APPLET
Sheet Cell Engine/Formula Issues
Issue: Extremely small numbers (both positive and negative) are not handled very well. Entering small numbers may lead to critical errors, InfoCenter problems, and file corruption.
Workaround: Do not enter numbers in the range of around 1e-295 and -1e-295.
Issue: Date numbers in the format of 01/14/1998 cannot be entered (they are converted to decimal).
Workaround: Use format similar to 1998/01/14.
Issue: Dates in the format of xx/xx/00 are interpreted as the year 1900.
Workaround: Do not use this format.
Issue: No recalculation setting is available from the user interface.
Workaround: This can be set through the applet API. The default setting is AUTOMATIC NATURAL.
Keyboard Shortcuts
Issue: Problems with keyboard shortcuts.
Workaround: Do not use keyboard shortcuts.
Font and Attributes/Borders Issues
Issue: Not all fonts are listed in Internet Explorer (SansSerif, Serif, Monospaced) These may cause failures in automation as well.
Issue: Editing a cell with a long label does not always clean up properly. You may see text left over in other cells while editing. This is cleaned up when using the edit mode has been completed.
Issue: Bold and Italic do not work at the same time with all fonts.
Issue: Borders do not always display correctly near the worksheet frame or when columns and rows have been resized or hidden.
Sorting Issues
Issue: Sorting when primary key column contains formulas causes unpredictable results.
Workaround: Make sure you are only sorting plain data or make sure the primary key column contains ONLY data.
Edit mode/In-Cell-Edit/Edit Console Issues
Issue: Backspacing does not always delete the character in Edit mode
Workaround: Use the arrow keys to put the cursor back in the correct place and press backspace again.
Issue: In-Cell-Edit mode does not end if you attempt to enter an invalid formula by pressing Enter. This may cause the selection of cells if you attempt to move the cursor around with the arrow keys.
Workaround: Press ESC, and re-enter the correct formula.
Issue: Entering data via the Edit Console and then clicking in another cell does not commit the data.
Workaround: Press Enter to commit the data.
@Functions (Range > Formula) Issues
Issue: @yield may return incorrect values due to number format problems.
Workaround: Make sure the cells contain the correct date number for the date you specified when using @yield with cell references.
Issue: Certain @functions (for example, @irr) are not accurate to 15 places. Functions are designed to be accurate to 7 places.
Range Name Issues
Issue: Focus problems occur in the range name edit control when selecting existing named ranges.
Workaround: Close the range name dialog and reopen after creating a few names or using existing names.
Issue: Deleting a column/row containing the first or last cell of a named range deletes the range name, causing the referencing formulas to display "ERR."
Workaround: Close the range name dialog and reopen after creating a few names or using existing names.
Issue: Pressing the name edit control of the InfoCenter does not create the range name.
Workaround: Click Define to create named ranges in the InfoCenter.
Spreadsheet Display and Print Issues
Issue: Working around the boundary areas of the sheet causes errors and display corruption. Scroll bars act unpredictably when you attempt to access boundary columns or rows.
Workaround: Stay away from the outer limits of the spreadsheet. If you must go there, use "Goto" to get to a cell. Note: Goto a "range" does not select the range, only upper left corner of the range.
Issue: Display corruption appears when the sheet contains various column widths and/or row heights.
Workaround: Refresh the screen. A pageup/pagedown will usually clear the screen corruption.
Issue: Sheet manipulation (for example, scrolling or deleting column and rows) causes display problems.
Workaround: Refresh the screen. A pageup/pagedown will usually clear the screen corruption.
Issue: Print jobs may not print (some jobs may queue but not print; other jobs do not queue or print) when running under Internet Explorer 4.01 or Netscape 4.04 This depends on the particular combination of printer and print driver that is being used.
Workaround: Print jobs sent to an HP III or IV using the appropriate print driver will generally print. Jobs sent to other combinations of printers/drivers may or may not print.
User Interface Issues
Issue: Some InfoCenter panels (dialogs) remain open after completing their commands.
Workaround: Continue to work while InfoCenter panels remain open. If you wish to close the panel (to see more of your spreadsheet, for example), then press the Done or Cancel buttons when finished with the panel, or the small "X" button in the top right corner.
1-2-3 Compatibility Issues
Issue: The eSuite spreadsheet applet is compatible with 1-2-3 Release 2.
Issue: Range Names are case sensitive. This is different from other 1-2-3 releases.
File I/O Issues
Issue: .WK1 files may display a block character in the edit line or the cell (browser dependent) for label and text strings.
Issue: Background images may not be clear (they remain in the background) when opening a new file or another file (Internet Explorer and Netscape).
Issue: eSuite HTML and HTML-WK file formats support UTF8 characters, so international or native characters do not display correctly.
Issue: System crashing occurs on NCD machines when you press the Shift-Insert key combination.
Workaround: Use Ctrl-V or the menu command.
Issue: System crashing occurs when you bring up the Choose Presentation Style panel and click OK without first selecting a new Presentation Style.
Workaround: Choose Cancel.
Issue: You notice a screen flicker (excessive redraws) on NCDs during screenshow on pages with bulleted lists.
Issue: Text fonts and Object colors may not be consistent across all platforms.
Issue: Graphic thumbnails do not render immediately when you first open the Presentation\Choose Presentation Style dialog. This does not happen all the time - it seems to depend on whether or not you are loading the applet over a network or locally, and on the speed of the network connection. Also, even if the thumbnails do not render properly, you can still select them and apply them to the presentation as usual.
Workaround: To remedy this problem try waiting a while or closing the dialog and opening it again later.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: The following Project Scheduler APIs do not immediately redraw:
Issue: The applet cancels after prompting you to save. This occurs when trying to open a document or getting a new scheduler after having made changes to the current applet. The applet prompts you to save but selecting "No" the first time actually causes the applet to cancel.
Workaround: Save your changes before trying to do a "New" or "Open" task.
Issue: When creating a new document, editing, or attempting to do a "New" or "Open" task, the applet does not prompt you to save.
Workaround: Save your changes before trying to do a "New" or "Open" task.
Issue: The project timeline does not redraw after changing timeline units. Redrawing does not occur until you click the dialog box.
Workaround: Click "OK" when you are done.
Issue: Clicking the browser "Back" button causes you to lose changes.
Workaround: Do not click "Back" until you have saved changes.
Issue: An error message is displayed when attempting to print using Internet Explorer or Netscape.
Issue: An error message is displayed when closing the Text Properties box using Netscape.
Issue: Context-sensitive HTML Help cannot be launched from the applet.
Workaround: With your browser, find and open the following file: ljups_contents.html. This will launch the top-level Table of Contents for the Project Scheduler Help.
**********************************************************************
SECTION 4: TEMPLATE BUILDER ISSUES
This section describes issues that are related to the eSuite Template Builder.
Issue: You need SUN Microsystems JDK 1.1.3 to work with the eSuite DevPack Preview Template Builder.
Workaround: If you don't have JDK 1.1.3, you can also create templates by loading the applet with LCAppletContainer and its InfoCenter, entering contents, and saving by choosing Save from the InfoCenter action bar.
**********************************************************************
SECTION 5: SAMPLE APPLICATION ISSUES
This section describes issues that are related to the eSuite Sample Applications:
ISSUES COMMON TO ALL OF THE SAMPLE APPLICATIONS
Issue: Users who sit behind a firewall need to make sure that the name of the server that is hosting the samples is contained in both the long and short form within the "proxy omit" settings of their client browsers. For example, if you are putting sample applications on a server within your firewall and it's FULL internet name is "hostname.domain.org". You would make sure that BOTH "hostname" and "hostname.domain.org" are in the browser's list of local machines that bypass the proxy.
Issue: Sample applications may not be accessible from remote locations
Workaround: This is likely to be an issue in an organization's network infrastructure. Typically, a security firewall will exclude remote use from a user attempting to access data inside a firewall. As "server-based" applications, the Customer Service, Parameterized Query, and Weather Chart applications are all subject to this. The solution is to place the server outside the firewall, or to permit selective access through the firewall. Consult your information systems staff for more information on accesing files through a firewall, as each organization's security system is different.
PARAMETERIZED QUERY APPLICATION
Issue: Problems occur when running the applet in Internet Explorer before 4.01.
Workaround: The applet requires Internet Explorer 4.01.
Issue: Problems occur running the Parameterized Query application even using Internet Explorer 4.01 or Netscape 4.04.
Workaround: You may have accidentally skipped an install step. Review the procedures in the Parameterized Query Application documentation for Installing and Running the Parameterized Query Application.
Issue: Incorrect Price and Sales data sometimes appears in the first row of the sheet after a query is submitted.
Workaround: This may happen the first time you run the query if you press the Submit Query button before the Applet is loaded. Watch for the browser status bar to indicate that the applet has been fully loaded. When the applet is done loading, you can then submit the query.
WEATHER CHART APPLICATION
Issue: Chart redraw problems occur when running the sample in Internet Explorer 4.01. One or more of the sample charts do not draw correctly.
Workaround: Refresh the page by Ctrl- Click the Refresh button. Scrolling the page will not correct this problem.
Issue: Weather Chart data does not seem to correspond to the location.
Workaround: The data pre-packaged with Weather Chart is sample data. You can enable "real time" weather reporting and display by following the Weather Chart installation / configuration documentation.
CUSTOMER SERVICE APPLICATION
Issue: The word processor applet does not load when you process a request.
Workaround: If you are working within a firewall, check your browser's proxy settings. Your server should be listed as an exception both by long and short name, for example, Long name "server.mycompanydomain.com" and short name "server.com."
**********************************************************************
The follow sections describe issues related to running your browser with eSuite applets.
Running eSuite with Netscape
Use the following procedure to run Netscape with eSuite applets:
Issue: eSuite is incompatible with certain Bongo classes.
Workaround: The Netscape patch for Java 1.1.4 installs Marimba Castanet, which includes a version of the Bongo classes. Due to eSuite's dependence upon a more recent version of Bongo, you must rename the "marimb10.jar" file so that it is ignored by eSuite. This file is installed in \netscape\communicator\program\java \classes. Note: Castanet will not be operable while this file is renamed.
Issue: Netscape Browser Cache Issues
Workaround: While browsers have options to regulate how to cache files retrieved from a server, you may experience some problems. To clear out the cache in Netscape do the following:
Running eSuite with Internet Explorer
Use the following procedure to run Internet Explorer with eSuite applets:
Issue: Browser-specific guidelines for scripting with eSuite.
When referring to a property, the correct syntax for Internet Explorer scripts is the following:
Issue: Help Index applet doesn't work when run locally in Netscape.
The Help Index applet is not functional when running with locally (i.e., file: URL) installed classes. It is only functional via the HTTP protocol due to security problems in Netscape. All other browsers can use the Help Index with either local or remotely installed classes.
Issue: Internet Explorer Browser Cache Issues
Workaround: While browsers have options to regulate how to cache files retrieved from a server, you may experience some problems. To clear out the cache in Internet Explorer do the following: