On Sun, Jan 14, 2007 at 03:54:23PM +0000, Thomas Adam wrote:
> On Sun, Jan 14, 2007 at 04:33:56PM +0100, Dominik Vogt wrote:
> 
> > With that, FvwmIdent prints the relevant information to the
> > console.  Can you post the output and the (relevant) output of
> > xwininfo please?
> 
> Sure.  I should just point out that I have tried this with FVWM having
> no config file to load up at all (just in case there was something in my
> own config file which might cause it).  Here's the output from the debug
> info from FvwmIdent and (selected) xwininfo output:
> 
>   FvwmIdent output:
> 
>   frame 492x340, bw 8, title 16(dir 0), client 484x316
>   client 484x316, base 0x0, inc 1x1
                                  ^^^

So fvwm thinks the character size is 1x1 (see below).

>   --> units 484x316
> 
> 
>   xwininfo output:
> 
>   xwininfo: Window id: 0x3c0000f "xterm"
> 
>   Absolute upper-left X:  4
>   Absolute upper-left Y:  20
>   Relative upper-left X:  0
>   Relative upper-left Y:  0
>   Width: 484
>   Height: 316
>    Corners:  +4+20  -792+20  -792-688  +4-688
>   -geometry 80x24+0+0
> 
> 
> Please note that I don't have ResizeHintOverride set anywhere, although
> this *does* indeed throw the numbers out, since it reports itself in
> pixels when I have turned it on.  Having spoken to a few people on IRC,
> they can confirm that FvwmIdent works fine for them, until they set
> ResizeHintOverride, at which point, the geometry string as reported by
> FvwmIdent is in pixels.  (I consider this to be a bug in itself, but
> that's a different issue as to why this still isn't working here for
> me).

The reason is that fvwm thinks the character size is 1x1.  This
happens explicitly with the ResizeHintOverride style (I've
committed a patch for that).  There are three possible reasons:

 1) The user set ResizeHintOverride

    ==> Try to set "style * !ResizeHintOverride" explicitly

    Note: This style does *not* work if the window is already
          mapped!

 2) The application did not set a character size (or any size
    hints at all).

    As xwininfo reports the proper size, this is not the case.

 3) The application set an invalid character size (<= 0)

    ==> look for a message "The application window ... has broken
        size hints (..._inc)" on the console.

> Thanks for your continual assistance on this, Dominik.

Ciao

Dominik ^_^  ^_^

 --
Dominik Vogt, [EMAIL PROTECTED]

Attachment: signature.asc
Description: Digital signature

Reply via email to