Below is a list of known problems and restrictions in the Motif versions of 
SQL*Forms 3.0, SQL*Menu 5.0, and Orakit as of 6/17/91.

------------------------------------------------------------------------------
  Sun specific notes
------------------------------------------------------------------------------

- IMPORTANT:  

  IF YOU ARE USING THE X11R4 SERVER, YOU SHOULD START THE SERVER WITH
  BACKING STORE TURNED OFF.  This can be done by calling xinit with the -bs
  option.

- There is a file, ".xmodmaprc", that is moved to $ORACLE_HOME by the install
  script.  This file enables the "META_L" (left Meta key).  It is put into
  use by typing "xmodmap .xmodmaprc" in $ORACLE_HOME.  It is recommended that
  ".xmodmaprc" be put in each user's home directory and the command 
  "xmodmap .xmodmaprc" be put in each user's .login, .profile, or .cshrc file.

- THE "Meta" KEY (shaped like a diamond, located on the left side of the 
  spacebar) ON THE SUN KEYBOARD IS THE EQUIVALENT OF THE "Alt" KEY USED WITH 
  ACCELERATOR KEYS.  The actual "Alt" key (located next to the "Caps Lock"
  key) does nothing.  Either use the "Meta Key" or use the utility "xmodmap"
  (See the man pages) to redefine the actual "Alt" key to be the "Meta" key.

-----------------------------------------------------------------------------
  Minor problems and restrictions:
-----------------------------------------------------------------------------

- There is a resource in the Orakit application resource file (should be put
  in $ORACLE_HOME by the install script) called "Orakit*Normal*fontName".  
  The size of all the windows of the Forms and Menu Motif applications will
  be smaller if this is set to "fixed".  The following message will appear if
  data is queried into a field of length 1:

  Warning:
      Name: tedit
      Class: XmText
      Invalid columns, must be > 0

  The text will also be chopped off in fields with 1 column until the user
  clicks on that field.  This is a Motif "feature" that will be fixed in later
  versions.

  Workaround:  Either use a proportional spaced font for 
	       "Orakit*Normal*fontName" or always make the display length 
	       for fields > 1.

- The "Show Keys" window is no longer a modal window, as in previous versions.
  It now can be brought up and left showing for easy access.  It is also 
  context sensitive, meaning functions that are not enabled in the context of
  what you are doing, are greyed out (but still visible).  This is still not
  done dynamically, however.  So when the user switches contexts, for 
  example, calling the "Trigger Definition" window from the "Screen Painter" 
  window, he or she will have to press Cntrl-K to update the window.  

- When a modal window pops up, navigation in the help system is disabled, e.g.
  when both the Help System and New Menu Application windows are on the screen,
  the scroll bars and buttons in the Help System window do not function.

  Workaround:  Dismiss the modal window before using the Help System.

- When a modal window is invoked from another modal window, navigation in 
  existing Show Keys window is disabled.  In the Menu Admin -> Security 
  window, if you invoke Show Keys followed by Grant Role, you then cannot use
  the scroll bars and buttons in the Show Keys window.

  Workaround:  Dismiss the Grant Role window before using the Show Keys
  	       window, or dismiss the Show Keys window before bringing up the
	       Grant Role window.

- In the SQL*Forms Designer form (as opposed to the spread table) version of
  the Field/Modify window, the "List of Values SQL Text" window is a 
  multiline text edit widget.  For any multi-line text edit widgets like 
  this one, the up and down arrow keys are taken from the widget by 
  SQL*Forms and used for "Previous record" and "Next record".  Therefore, for
  vertical navigation, use "Previous Page", "Next Page", "Scroll Up" or "Scroll
  Down".

- The Cut, copy and paste function keys do not work perfectly in Runform.
  For example, you sometimes have to hit the Paste key twice for it to work.
 
  Workaround:  Use the top menu "Edit" item to cut, copy, and paste in Runform.

- The "Clear field" (CLRFLD) functions in Runform, works only if the cursor
  is at the beginning of the field.

- The <List> message does not appear at the bottom right of the main window
  in SQL*Forms Designer when the File/Open option is chosen, even though 
  the ListValues key functions properly.

- The DISPLAY_FIELD packaged procedure has no effect on text widgets.
  This applies to Runform fields.

- In the Screen painter of SQL*Forms Designer, the screen is not updated if 
  a selection is undone or aborted.  If you place at least one of your select 
  points on the edge of a field box and then press the undo key, the select 
  marks will go away, but a hole is left where the select point used to be.

  Workaround:  Scroll this point out of view and then back into view.  We 
  	       recommend not placing your select points of existing text or 
               objects.

- In Runmenu, when using "Bar" type menus in Runmenu to execute a 
  SQL*Plus statement which includes a "pause", the process is stopped.  The 
  cursor focus remains with the application and cannot be released except 
  by killing the Runmenu process.

  Workaround:  Don't use "pause" in SQL*Plus statements executed through 
  	       "Bar" type menus.

- Can only enter 30 characters in dialog boxes, e.g. Load Form, even though
  field displayed is longer.


-----------------------------------------------------------------------------
  Items deferred to the next release:
-----------------------------------------------------------------------------

- Hiding of Dialog Windows and Alert Boxes when the main window is iconified.
  Return visibility when main window is de-iconified.

- Add hourglass/watch cursor during waits.

