$Id: KNOWN-PROBLEMS-ot,v 1.17 2004/12/16 13:06:58 tcanavan Exp $

			    OBSERVING TOOL



KNOWN PROBLEMS FOR 2.9beta4


Printing needs to fixed so everything can fit on a page 

USG File Integration

KNOWN PROBLEMS IN V.2_9beta4
****************************************

[2652] With database/repository browsers, when a large data set is queried and
       the Break and Query buttons are pressed many times, rapidly,
       in succession, the application may get a database error
       (and message box) similar to the following:
       
           ERROR - Fatal SQLException in Dbase IO Thread
           java.sql.SQLException: JZ006: Caught IOException: 
               java.net.SocketException: null
               ...
               ...
           ERROR - database query failed
           
       There is no workaround, it is advised to restart the application in
       such an event.

[1616] When displaying the OB History the default should not be to
       display the whole table as this is huge


[2186] Trying to delete a configuration in any Database Browser
       causes a cannot find error message if it is created in the
       current session. Current workaround exit application and then
       delete the configuration

[2003] The generation of a GIF file from a VisiPlot in OT is slower
       in Java1.4 compared with Java 1.1.8. This issue has not been
       investigated.

[1968] See 1985 below.

[2036] When running Java 1.4 applications on Solaris, and displaying
       on Linux, certain window managers (Gnome and KDE are known)
       result in the delete (DEL) and backspace keys not working.

       This is a known bug and will be investigated when information
       is available as to under what circumstances the problem occurs.

       Workaround: ctrl-h works as a work around.

[2489] When running Java 1.4 applications on Solaris, and displaying
       on Linux, one may get a list of warnings like:
           Warning: Cannot convert string "<Key>Escape,_Key_Cancel" 
	   to type VirtualBinding 
       This can occur for any X application and on any platform.  For
       example, users have reported seeing this when running emacs,
       nEdit and many other programs and java applications too - on
       Unix, Linux and BSD.

       Possible workarounds are:

       1. Ignore the warnings; they are annoying but there appear to
          be no negative consequences.

       2. One can also prevent the warnings (at least some of them) by
          typing:
              xprop -root -remove _MOTIF_DEFAULT_BINDINGS
	  before starting the application.
	   
[1985] Combo Boxes which display the drop-down list outside of the
       window frame will be displayed behind the main window frame
       when moving the drop-down list scroll bar. This occurs on some
       CDE (dtwm) sessions.

       Work around: run the command dtstyle (/usr/dt/bin/dtstyle) ,
       select "Window", and ensure the option: "Allow Primary Windows
       On Top" is NOT checked.

       Explanation:

       This is a reported Java1.4 bug (#4781582), which is "in progress".

       When a combo box displays out side of the main window frame, it
       is represented with a "heavy weight" component (i.e. a window,
       managed by the window manager).

       This heavy weight window, in combination with the window
       manager style setting allowing a parent to be displayed in
       front of the child, means the combo box list dropdown will fall
       behind the main window.

[xxxx] Visiplots: grouping identical OBs for display may result in a
       long list of OB ids. If this list is long, it will extend off
       the edge of a printed page or mis-shape the plot. The list
       needs to be re-organized to be displayed over multiple lines.

[xxxx] Visiplots: while the display and printing of plots has been
       optimized for minimal graphic memory usage, the saving of plots
       to GIF files still uses a considerable amount of memory and
       _may_ present problems for some Xterminal environments. When an
       Xterminal is running on less than 1 Meg memory, the behaviour
       of graphical applications may become unpredictable.

[1114] Breaking a long query in the Repository Browser (several
       hundred OBs) might sometimes cause problems. We're
       investigating to understand why.

[1147] Foreign key constraint violation?  Could not be reproduced.

[1167] Append new OB to a queue: nothing happens.
       Could not be reproduced.

[1169] NullPointerException generated by NextObsBlocks 
       Could not be reproduced.