Conference hydra::axp-developer

    Called customer back with information on how to set up, at a system
    level, the activation of overlay planes.  You need to make two changes,
    the first is to add a new file called .Xdefaults in your log in (home)
    directory and insert the following:
    
    	Dtsession*wmStartupCommand: /usr/dt/bin/dtwm_overlay -Overlay
    
    Second, you need to add to /usr/Dt/app-defaults/C/Dtwm
    
    	Dtwm*0*overlayColorUse: FOUR_COLOR
    
    (Notice that capital letter usage is critical.)
    
    I told him I would call back with information on when Open3D v4.3
    starts to ship, as it includes bug fixes and enhancements.
    
    It also turns out that you need to call a completly different window
    manager to get overlay plane support ie - dtwm_overlay

    Called customer back to see if recommended changes helped.  He said
    that they did not seem to solve his problem.  I stated that if I were
    going to log a QAR with engineering, they it would need to be against
    the latest shipping version of Open3D, which is v4.3 (FCS 4/97). 
    
    I sent him out a new kit and will call next week after it is installed,
    to see what problems still persist.

    Called customer to see if layered products CD arrived.  It did not,
    will call back tomorrow.

    Called customer and he asked me to call him back later.

    Called customer back and he had received the open3d kit I sent him.
    
    I walked him through the process of loading the new software on his
    system.  I verified that the correct switches were set to use the
    overlay window manager.
    
    I will call him back next week to see if his problem still persists,
    after he has had time to use the new open3d software v4.3 kit.

    Customer called back on 5/13 in a panic because his system would not
    run Open3D graphics on boot up.
    
    After reviewing the system setup with him over the phone, I determined
    that they had a miss-match set of Open 3D v4.2 and v4.3 kits installed.
    Once they made all options at v4.3, the system would boot correctly.

    Called customer back on 5/15 to check on status.  They are still having
    problems with Overlay Windows switches.  It is OK when they don't ues
    overlay windows.  There are four settings that they want to use:
    	12 bit psuedo color, double buffered
    	8 bit pusedo color, double buffered
    	24 bit true color with 4 planes for overlays
    	24 bit true color no overlay planes
    They are getting the following error with overlay planes:
    	GLX bas current window, major opcode of failure request is 139,
    	minor is 1.  Serial number of failed request is 5326.
    
    
    
    
    

    Called customer back on 5/20 and verified that he was using one
    seperate window for his graphics window and another seperate window for
    his overlay planes.  
    
    Confirmed that he should be using "glXChooseVisual" to determine what the 
    correct visual type is that he should be using.  He is using the
    following visuals for TrueColor ID 26, Psuedo Color ID 30 and for
    Overlays ID 32.
    
    He is having a problem with CDE with it constantly clearing his display
    image.
    
    I had suggested that he use is Dtwm the setting "Four_color", and
    requested that he change it to "low" for 10 color support.
    
    He said that he needed to go back through his code to verify that he
    had not changed anything that might break his code.  He had made a lot
    of changes to the code base in trying to get overlay planes to work on
    DEC UNIX.  I said I would call him back to see how it was going.
    
    

    Called customer back on 5/27, he was not in and I left him a message.

    Called customer back on 5/30 and he was not in office.

    Called customer back.
    
    Told him of new problem with Open3D v4.3 on Unix with system hanging
    after 49 days in use.  He is about 4 weeks away from this hang problem. 
    Gave him pointer to http://www.service.digital.com/open3d/ so he could
    pull the patch to fix this problem.
    
    He had mentioned a problem with slow feedback delays from moving the
    mouse and when his window or display information got updated, in a
    prior call.  In going through the Open3D notes file, I found note #1189
    that said to add to the $HOME/.Xdefaults file the following line:
    	*freezeOnConfig: True
    
    I will call back later this week to see if he got the patch and if this
    change to the .Xdefaults file fixes his problem.
    
    He stated that he now seeing Overlay Window problems on his IBM port as
    well, that are similar to the DEC problems.  He said he doesn't have
    time now to fix this Overlay Window problem and will most likely
    disable it for DEC & IBM for this release and fix it at a later date.