"Valeriy E. Ushakov" <[EMAIL PROTECTED]> writes:
> Hi, Dan.
> 
> I'm a JavaSoft contractor for AWT group.  There are several bugs filed
> against jdk running under fvwm2.  Several of them are caused by a
> problem with interpretation of gravity in configure requests.  See my
> mail below.

Hi,

  To reach the developers supporting Fvwm, you need to
use the email address [EMAIL PROTECTED]  I'm forwarding
this.

> Thanks.
> 
> PS: I hope that weird awt top-level insets problems under fvwm2 went
> away with JDK1.4.
> 
> On Mon, Aug 05, 2002 at 08:31:29PM +0400, Valeriy E. Ushakov wrote:
> 
> > On Fri, Aug 02, 2002 at 03:59:34PM -0700, Gordon Prieur wrote:
> > 
> > > > However, I have no objection to your forwarding it: the 
> > > > Evaluation section of the bug report is intended to be 
> > > > publically available.  BTW, I'd love it if fvwm developers 
> > > > could add an option to handle the window gravity issue. 
> > > 
> > > They claim they already do. Thats why I got involved. It looked like
> > > the clasical case of 2 groups saying the problem is the other groups.
> > > I hope to get them talking to your group, but first I wanted to give
> > > them the updated evaluation.
> > 
> > <[EMAIL PROTECTED]:~> (2029) fvwm-config --version
> > 2.4.8
> > <[EMAIL PROTECTED]:~> (2030) wish
> > % wm geometry .             # window at +0+0
> > 200x200+0+0
> > % wm geometry . +1+1                # window decor is moved off-screen
> >                             # i.e. client is at +1+1, not decor
> > 
> > Other window managers that have this problem are IceWM and
> > Enlightenment.
> > 
> > Running these same wish commands under, e.g., olwm places the window
> > correctly.
> > 
> > I'm not sure what's the problem might be, but enabling debug messages
> > in fvwm and adding few more in HandleConfigureRequest I can see e.g.
> > java requesting a window positioned at (3,11):
> > 
> > TL: reshape(0x24d058/0x2c00041,
> > TL:         x = 3, y = 11, w = 153, h = 195, setXY)
> > 
> > and fwvm doing:
> > 
> > [UWE] ConfigureRequest: x=3 y=11
> > [FVWM][SetupFrame]: <<DEBUG>> Routine Entered (x == -4, y == -18, w == 153,
> > h == 195)
> > 
> > I.e. x and y are off by decoration size (left=7, top=29).
> > 
> > 
> > A simple Xt test case that does this when window is already mapped:
> > 
> >     XtVaSetValues(toplevel, XtNx, 5, XtNy, 5, NULL);
> > 
> > has the same problem too (the above code was just added to xlogo to be
> > called on XtAddAppTimeOut).
> > 
> > -uwe
> 
> -uwe

-- 
Dan Espen                           E-mail: [EMAIL PROTECTED]
444 Hoes Lane  Room RRC 1C-214      Phone: (732) 699-5570
Piscataway, NJ 08854
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to