discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with larswm


From: Björn Gohla
Subject: Re: problems with larswm
Date: Wed, 24 Oct 2001 10:17:31 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 19 October 2001 18:44, Björn Gohla wrote:
> i have been trying out larswm as a window manager
> (http://www.fnurt.net/larswm), most importantly it does not provide for
> means to move windows with the mouse, but instead it tiles them into the
> screen according to predefined rules. this makes it look a bit like oberon,
> where you have a broad "user track" on the left side of the screen and a
> narrow "system track" on the right. after heavyly editing the config file
> it is even possible to work with it ;) . so far so good. the problem with
> gnustep apps here is that apart from not beeing able to move the menu
> around (AFAIK gnustep is responsible for placing the menu) also clicking on
> menu items has no effect.

these are some observations i made, perhaps they provide a hint as to what 
the cause of the problem could be.

all windows of several gnustep apps answer the following to xprop:

WM_HINTS(WM_HINTS):
                Client accepts input or input focus: False

the events sent to the menu of a gnustep app during the pressing of a mouse 
button are these:

LeaveNotify event, serial 11, synthetic NO, window 0x1400021,
    root 0x2b, subw 0x0, time 3183250846, (71,86), root:(73,88),
    mode NotifyGrab, detail NotifyAncestor, same_screen YES,
    focus NO, state 256

EnterNotify event, serial 11, synthetic NO, window 0x1400021,
    root 0x2b, subw 0x0, time 3183251616, (71,86), root:(73,88),
    mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
    focus NO, state 0

KeymapNotify event, serial 11, synthetic NO, window 0x0,
    keys:  43  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  

while the window manager receives corresponding EnterNotify, ButtonPress, and 
LeaveNotify events. perhaps somebody more knowlegeable can tell wether my two 
observations are related and if so, why gnustep seems to always set the above 
mentioned window property to false, while other frameworks seem to prefer it 
the other way. alternatively, if the mentioned window manager hint is indeed 
correct, what is larswm doing wrong that other windowmanagers are doing right 
(windowmaker and kwm anyway) ?

i would be grateful for any hint.
- -- 
- --------------------
"go, wash the dishes!" "can't we do that with a perl script?"
pub  1024D/834F4976 2001-01-07 Björn Gohla (Wissenschaftler, Weltbürger) 
<b.gohla@gmx.de>
     Key fingerprint = 9FF4 FEDA CCDF DA0E 14D5  8129 6C14 3C39 834F 4976
sub  1024g/29571FE2 2001-01-07
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE71nkfbBQ8OYNPSXYRAqoEAKCLukFqrJEyIeUOg58LvitMCWW2GwCfRwpA
yN30OtJsRccelJk7aFdvnvE=
=aaDL
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]