CLIM 1.0 bug

• To: mthome@BBN.COM
• Subject: CLIM 1.0 bug
• From: John Kern <kern%kuwait@lucid.com>
• Date: Tue, 3 Mar 92 10:50:33 PST
• Cc: clim@BBN.COM, clim-support@lucid.com
• In-Reply-To: mthome@BBN.COM's message of Tue, 03 Mar 92 11:07:54 -0500 <9203031654.AA29576@lucid.com>
• Reply-To: kern@lucid.com

Howdy,

I believe this is fixed in the forthcoming 1.0 release.  If you
provide me with a short reproducible testcase I can confirm it.

Sincerely,

John S. Kern
Lucid, Inc.
Customer Support


==== original message for easy of reference ======================
In Lucid CLIM 1.0b (10-jun-91, patches through #6063) on Sparc, SunOS
4.1, X11R5 server...

	If a CLIM frame is manually reshaped (i.e. via twm window
decorations), the frame (and subcomponents) reshape correctly, but the
pointer highlighting but *not* the actual sensitivity gets shifted
from the frame's origin to the parent screen's origin - i.e. if the
frame is positioned at (50, 100) on the screen and output record A is
at (200, 300) on the frame, reshaping the frame results in:
	1. clicking at (200,300) in the frame does the right thing -
activates a command associated with output record A.
	2. But output record A only *highlights* when the pointer is
at (200,300)-(50,100)=(150,200)!
	
This is true for all window streams within the frame, and is fixed by
*repositioning* the frame.

	-mik (mthome@bbn.com)

• Prev: Incremental Redisplay Performance
• Next: Speeding up CLIM startup time.
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)