home *** CD-ROM | disk | FTP | other *** search
- X Window System Update for OS/2 TCP/IP 1.2.1
- Version 1.2.1.3
- 1992 July 22
-
- INSTALLATION
-
- The OS/2 TCP/IP 1.2.1 "refresh" base must already be installed. The X
- Window System option also must already be installed, and the XFILES
- environment variable must have been defined as a part of this process.
- It does not matter if earlier beta test versions have already been
- installed or not. This version does not contain the complete X Window
- System option for TCP/IP 1.2.1. It only has things that have changed
- since the release of 1.2.1.
-
- If PMX is running, stop it before trying to install the update.
-
- Put the first (or only) update diskette in a diskette drive, and run
- INSTALLX on the diskette. For example, if the diskette is in the a:
- drive, type at a command prompt:
-
- a:installx
-
- Note for those maintaining LANs: If the files from the diskette(s)
- are copied to a directory of a shared disk on your LAN, you should be
- able to run INSTALLX from that directory to install the update.
- You will want to use the "-logpath dir" command line option, to
- cuase the PMX.LOG file to go to a private directory, rather than the
- shared XFILES directory.
-
-
- WARNING ABOUT NEW COLOR FEATURES
-
- This version is much less "beta code" than the previous. Please
- read the on-line documentation about color support! A brief
- summary follows, but not all details are covered.
-
- If you do not specify -pseudo on the command line, then -static
- will be the default. However, if PMX discovers that the PM
- device driver supports modifiable color tables, the default will
- be -static -pseudo. In the latter case, most X client that try
- to modify color tables will NOT discover that they can do so, by
- making a request for the PseudoColor visual. Also be warned that
- a number of PM device drivers, epecially in OS/2 2.0, do not say
- that they can support modifiable color tables, when in fact they
- can. If you want it, you will have to say -pseudo on the command
- line.
-
- Be warned that ordinary VGAs do not support -pseudo. If you chose
- "seamless windows" for running Microsoft Windows programs, then
- you will get VGA mode, and -pseudo will not work.
-
- We attempt to not modify system colors; this is much better than
- before. We also restore them more nicely, and you have a couple
- of menu options on the server window to control this.
-
-
-
- WARNING FOR OS/2 2.0 USERS
-
- We have done more testing with 2.0, but still have known problems,
- even though we have fixed a number of problems and programmed around
- some others. The major ones are listed below in the bug lists.
-
-
- FIX SUMMARY
-
- - version 1.2.1.3 - July 22, 1992 - This version fixes several
- problems: For OS/2 2.0, there was interference between REXEC and PMX.
- This has been worked around by giving PMX a higher priority class.
- ICCCM conventions are observed for the minimum and maximum sizes of
- windows. Z order bugs are fixed. Some changes were made which should
- fix a number of problems to do with task list entries. However, not
- all reported problem situations could be tested for.
-
- - version 1.2.1.2 - July 13, 1992 - This fixes a problem with PM heap
- overflow that affected several users, and fixes a problem with the
- sequence maximize-minimize-restore. There are also more fixes for the
- Japanese keyboard. Some sloppiness of positioning of the application
- withing the PM frame is also fixed for some applications. We expect
- to get out another version before the 24th of July.
-
- - version 1.2.1.1 - June 24, 1992 - This fixes the keyboard mapping
- problem that was in the previous version. It was seen if you ran
- xmodmap (or xinit.cmd). A bitmap related problem also is fixed.
- Unless there are glaring problems, this will be available as a CSD
- around the end of June. We expect to get another CSD out in July.
-
- - version 1.2.1.03 - June 19, 1992 - This version fixes a number of
- problems with 1.2.1. Also focus handling is MUCH closer to normal PM
- focus handling. If you click on a client area, the window will come
- to the top, for example. In 1.2.1 if you closed a window and the next
- window that had focus happened to be a OS/2 command window or an
- aixterm window, that window had the keyboard locked. This is now
- fixed. Support for Japanese keyboards is more correct. We found it
- was necessary to turn off PM support for double byte mode, so that the
- X application could see the correct keystrokes. A menu problem with
- Interleaf has been corrected.
-
-
- ----------------------------------------------------------------------
- In the sections below are major remaining known bugs and things still
- not implemented for PMX.
- ----------------------------------------------------------------------
-
- - Window manager hints -
-
- Not all "window manager hints" are paid attention to as yet. We do
- pay attention to most. Mainly missing is the use of client specified
- icons, colormap conventions and some size conventions, such as
- "increments" and "aspect ratios" of width and height.
-
-
- - Grab Implementation -
-
- "Grabs" are not completely supported yet. While the cursor is outside
- of any X window, no X client has control of focus. X clients do have
- control if the cursor is inside some X client window. Also no drawing
- can be done outside of X windows, so no client could draw a "rubber
- band" or "resize rectangle" outside of the X windows, into PM
- territory. Otherwise X "grab" behavior is supported.
-
-
- - Background window scrolling problem
-
- There is a known problem in the current product version of the OS/2 X
- server in some circumstances where a PM window or PM frame of an X
- window is on top of an X window. If the X window in the background is
- "scrolled", pieces of the PM frame or PM window can become part of the
- scrolled data. This situation is easily corrected by "refreshing" the
- contents of the X client window. (E.g. select "refresh all clients"
- from the PMX Command pull-down menu, or raise the background window to
- the top by clicking on its frame.) [We are expecting to fix this
- fairly soon.]
-
-
- - Cursor limitations
-
- If an X client creates a cursor using bitmaps that are larger than
- 32x32, the portion in the lower left corner is used, instead of the
- portion around the "hot spot". The result may be an incorrect
- appearing cursor. The user may avoid using cursors created by X
- applications by starting PMX with the -noxcursor parameter.
-
-
- - PM Device Driver Problems
-
- Some PM display drivers do not implement certain graphic operations
- efficiently, and as a result, some types of text display or
- "stippling" are slow on some displays. We have programmed around
- these PM deficiencies as best we could, and we expect future versions
- of PM drivers to improve these operations. We also have some command
- line options that can affect this. As of the shipping of this update,
- several PM device driver bugs and limitations exist. (1) The XGA
- drivers for both OS/2 1.3 and 2.0 and the 8514 driver for 2.0 all have
- a bug where very tall bitmaps are not supported correctly, and their
- data can be stored over other bitmaps. This causes some X fonts to
- display incorrectly, and sometimes even PM window titles in non-X
- windows have been garbled! The work-around is to run with the -xga
- flag, although this slows things down. The problem can still happen,
- if an X application creates a bitmap that is much larger than the
- screen in the X or Y direction (4096 pixels or above). (2) OS/2 2.0
- has some severely low system wide limits on the number of PM bitmaps
- that can be created. If you use the -nofbm command line option, PMX
- will not use PM bitmaps to store fonts, at the price of reduced text
- speed. Note that the -xga and -nofbm flags actually do the same thing
- at this point.
-
-
- - Response to PM cursor and keyboard events
-
- When initializing or shutting down PMX, the cursor and keyboard are
- not responded to; we attempt with limited success to display the hour
- glass cursor in such situations, but really should just let the cursor
- and focus go anywhere the user wishes.