[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::excursion

Title:note 3 has pointer to current kit
Notice:note 3 has pointer to current kit
Moderator:PEACHS::GHEFF
Created:Wed May 29 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3301
Total number of notes:14905

3260.0. "probl. displ. amds on eXc3.0.554" by ATZIS1::SCHNABEL (Plus en plus seule...) Wed Apr 09 1997 09:17

    Customer displays DECamds from an AXP/VMS6.2 via TCP/IP
    on the PC running eXc. V3.0.554 under NT V4.0.
    
    Both amds-windows came up fine but after resizing
    one of the windows (for example process view)
    it starts to flicker.
    
    Now the only way to get rid of this situation is to
    kill the amds-window.
    
    We think that the problem only appears with windows
    which are heavily updated. (not seen on standard 
    decwindows applications)
    
    thanks for any help
    Werner
T.RTitleUserPersonal
Name
DateLines
3260.1PEACHS::GHEFFGot a head with wingsWed Apr 09 1997 15:459
    I have an elevation on its way up that looks to be similar.  An
    application named VXL causes the mwm window borders to flash at 1/2
    second intervals.  And in some cases the contents of the window
    flashes.  (Note, I saw flashing behavior during the field test with Netscape
    Navigator and xv, but this cleared up in the SSB release.)  I have 
    trap file that clearly shows what the customer is seeing.  (It'll be
    pointed to by my IPMT case.) 
    
    #Gary
3260.2please let meknown the number of your IPMT ATZIS1::KARTNER_MHOUSTON, we have a problemThu Apr 10 1997 06:358
    Hi Gary!
    
    I'm the "owner" of the stated problem. Could you please let me
    known the number of your IPMT so that our escalation manager is
    able to track the escalation ?
    
    				thanks for your fast response
    				Michael 
3260.3PEACHS::GHEFFGot a head with wingsThu Apr 10 1997 13:054
    Don't have one yet.  It's still working its way through our review
    process.
    
    #Gary
3260.4Allready an ipmt ?ATZIS1::KARTNER_MHOUSTON, we have a problemFri Apr 18 1997 08:317
    Hi Gary!
    
    Have you got any news concerning this problem? I you haven't escalated
    till now I'll do so on monday
    
    								thanks
    								Michael
3260.5JAMIN::OSMANEric Osman, dtn 226-7122Fri Apr 18 1997 13:4828
    
    As you diagnose these flickering problems, please distinguish between
    the following cases:
    
    o	The dueling icon case
    	---------------------
    	In this situation, two mwm icons, or an mwm icon and a an ms window
    	title bar, flicker indefinitely due to focus being switched back
    	and forth between them.
    
    o	color-update flicker case
    	-------------------------
    	In this case, if one x application has focus while another x
    	application is performing "XAllocColor" calls, the focused one
    	flickers once per XAllocColor (since the XAllocColor may have
    	changed the colormap and hence the focused app needs to be redrawn
    	in the possibly new colors
    
    Please determine which case you're seeing.  For example, for the
    dueling icon problem, if you have another mwm icon up, and you click on
    that icon, does the flickering stop ?  What if you use builtin wm
    instead of mwm ?  Does flickering still occur ?
    
    With the color-flicker, if you use the 256-color model (in your ms
    display control panel) instead of 65000-color model, does less
    flickering occur ?
    
    /Eric
3260.6PEACHS::GHEFFDo you feel like swimming?Fri Apr 18 1997 17:2121
    Hi Eric,
    
    My particular issue -- and now I have 2 customers with the same one --
    would be the second of the 2.  I've seen the dueling mwm before and it
    never really struck me as much of an issue since you can shut it up
    pretty easily by playing with the icons.  The second issue is more
    serious.  Yes, 256 colors does cure it.  No, most customers are not
    interested in that as a longterm solution.  (We saw a *lot* of calls on
    this back in the days of eXcursion 1.2 which would behave badly when
    Windows was set for 16 or 24 plane color.  Which drove the development
    of the 2.1 code to deal with 8-bit pseudo visuals in the 16 and 24 plane
    modes.)
    
    The simplest test to reproduce this is to run xgif in a dxterm window.
    Xgif is not a standard dunix component, but if you don't have it, you
    might be able to dig up xv.  (Xv shipped as part of the eXcursion SDK,
    fwiw.)  When I run xgif to bring up a relatively small gif file (160K)
    it takes nearly 4 minutes to load on a system set up with 16bit color.
    (And about 10 seconds on one in 8bit.)
    
    #Gary
3260.7neiter 256 colors nor toggling of windows did helpATZIS1::KARTNER_MHOUSTON, we have a problemWed Apr 23 1997 13:5212
    Hi!
    
    I've tested your suggestions for our AMDS problem but
    
    	a) switching to 256 colors didn't change anything
    	b) toggling with other windows (decw$clock,..) didn't help too
    
    The only way to "solve" the problem is by killing the Task and
    start AMDS (via Excursion) again
    
    							thanks
    							Michael 
3260.8PEACHS::GHEFFDo you feel like swimming?Wed Apr 23 1997 15:076
    In that event, I suspect that your problem is different from the ones
    I've seen.  Both of them were curable by dropping to 8 bit color.
    
    If you haven't already, I suggest you get a trap file.
    
    #Gary