Xref: utzoo comp.windows.open-look:358 comp.windows.x:31187
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!milano!uudell!bigtex!texsun!newstop!exodus!trantor.Eng.Sun.COM!smarks
From: smarks@trantor.Eng.Sun.COM (Stuart Marks)
Newsgroups: comp.windows.open-look,comp.windows.x
Subject: Re: Trouble with olwm
Keywords: olwm resize MinimalDecor
Message-ID: <5276@exodus.Eng.Sun.COM>
Date: 4 Jan 91 20:58:03 GMT
References: <1990Dec28.000047.23748@agate.berkeley.edu>
Sender: news@exodus.Eng.Sun.COM
Reply-To: smarks@eng.sun.com
Followup-To: comp.windows.open-look
Organization: Sun Microsystems, Inc.
Lines: 28

In article <1990Dec28.000047.23748@agate.berkeley.edu>,
welch@csua.berkeley.edu (Sean N. Welch) writes:
|> I've run across a
|> slight problem in resizing windows that have MinimalDecor. 
|> 
|> When you select a resize corner, instead of the rubberband surrounding 
|> the window, it appears as a vertical line on the opposite side of the
|> window, and upon release of the SELECT button, the window resized itself
|> to several times the width of the screen.  
|> 
|> Now this only happens on clients that have the MinimalDecor resource 
|> set via xrdb.  Clients that have the no header hint set internally,
|> such as perfmeter, don't seem to have this problem.  

This is a bug in olwm.  The problem is an uninitialized variable
(decorWidth) in the makeSpecial() function in winframe.c.  If you
fix the declaration to initialize decorWidth to zero, the problem
should go away.

Thanks to Robert Giovannucci <bobg@ll.mit.edu> for pointing
out this bug.

s'marks

-- 
Stuart W. Marks			ARPA: smarks@eng.sun.com
Windows & Graphics Software	UUCP: sun!smarks
Sun Microsystems, Inc.