[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

3257.0. "Loss of Scrolling Details on Partially Covered Windows" by FUTURS::tuna08.reo.dec.com::BURRELL (Live Long-Prosper/Live Short-Enjoy!) Mon Apr 07 1997 06:07

	I don't know if this has been covered in the conference.
	An initial look at keywords and titles didn't show anything...

	Since upgrading to Xcursion V3.0.554 the following "feature" has
	appeared.

	If two Xcursion windows are overlapping - then any scrolling display
	on the covered window looses the scrolling display vertically
	from the point where the windows overlap. I have been informed
	that this may be down to the window not receiving an "Invalidate
	Rectangle" command.

	Has this been noted before - an if so - is there a solution?

	I realise that this isn't a major problem with the application -
	which I prefer over all the other terminal emulators around -
	but it has only occurred since the upgrade.

	Paul.

T.R Title User Personal
Name Date Lines

3257.1 JAMIN::OSMAN Eric Osman, dtn 226-7122 Tue Apr 08 1997 13:32 22

T.R	Title	User	Personal Name	Date	Lines
3257.1		JAMIN::OSMAN	Eric Osman, dtn 226-7122	`Tue Apr 08 1997 13:32`	22
	The problem you notice is due to the server not generating a VisibilityNotify event to the dxtern window when its visibility changes. dxterm has an optimization that causes it to ignore exposures when it thinks it is unobscured. Since the server doesn't tell dxterm that is obscured, it doesn't honor the exposures generated for the regions scrolled out from under the occluding window above. This has recently been fixed and will appear in the next release of the server; however, this fix only provides a partial fix. In the Windows environment, it isn't possible to know when a window from another applications occludes one of eXcursion's windows. For this reason, you will still notice the problem when you cover a dxterm with a window from another Windows application. This problem can't be fixed. As for why you only noticed this problem in the current release, I don't have an explanation - this problem has always been in the server.

The problem you notice is due to the server not generating a VisibilityNotify
    event
to the dxtern window when its visibility changes.  dxterm has an optimization
    that
causes it to ignore exposures when it thinks it is unobscured.  Since the server
doesn't tell dxterm that is obscured, it doesn't honor the exposures generated
for the regions scrolled out from under the occluding window above.

This has recently been fixed and will appear in the next release of the server;
     however,
this fix only provides a partial fix.  In the Windows environment, it isn't
    possible to know
when a window from another applications occludes one of eXcursion's windows. 
    For
this reason, you will still notice the problem when you cover a dxterm with a
    window
from another Windows application.  This problem can't be fixed.

As for why you only noticed this problem in the current release, I don't have an
explanation - this problem has always been in the server.