[PyWM-talk] [Fwd: Re: My initial pywm fumbling and a window handling bug]

[<el...@ji...>]

-------- Original Message --------
Subject: 	Re: [PyWM-talk] My initial pywm fumbling and a window handling
bug
Date: 	Thu, 04 Jan 2007 17:01:47 +0200
From: 	Elmo M=E4ntynen <el...@ji...>
To: 	Nils Olav Fossum <ni...@no...>
References: 	<200...@no...>



Nils Olav Fossum wrote:
> hi to all 11 of you :D
>
> I have started to look at pywm to use on a touchscreen carPC.
> The touchscreen is a Lilliput 7" with 800x480 resolution.
> pywm seems like a good wm to use to run applications like GPSdrive on..
>
> I really need to get controll over the application windows..
> ..but there is a bug in the window-handling code somewhere..
> The windows dont register as they should do.
>
> in the __init__.py file, WM class, we have _addWin, _delWin and window
> I had to manipulate these to get the window registering working.
> See the attached patch.
> This is just a hack so I can go on testing pywm, but I hope someone can=
 take a=20
> look at it to locate the real bug..
>
>
> So a question..
> I use Xnest for testing pywm because a 7" 800x480 sized screen is less =
than=20
> comfortable to work on.
>
> When I start my pywm derivate (wm1.py), on a new Xnest with no applicat=
ions,=20
> something goes wrong and I cant get my test Fl_Window to receive mouse =
click.
> Started like this:
> $ Xnest -ac -geometry 800x480 :22 &
> $ export DISPLAY=3D:22
> $ ./wm1.py
>
> However when one application is running inside Xnest before I start wm1=
.py it=20
> works.. (Started like this):
> $ Xnest -ac -geometry 800x480 :22 &
> $ export DISPLAY=3D:22
> $ xclock&
> $ ./wm1.py
>
> So , is this another bug, or is it something  I dont do right..?
>  =20

Probably a bug. Can't tell, since I got too much on my hands at the momen=
t.

> I have attached wm1.py as a simple test wm.
> Shift-a  will launch a rxvt console
> Shift-s  will print out the 'WM.windows' dir and 'WM.windowlist' list c=
ontent=20
> for debugging of window-handling.
>  =20

You should consider using trying the darcs vcs. The tarball is a darcs
repo (a branch), with which you can work with (it works without a
central server, but I could set one up if deemed useful). Notice that
your patch has tabs in the last part. Also, you might want to take a
look at Leo, the editor (or ide) that the original author used. Because
of the learning curve (not that steep) associated with efficient usage,
I haven't used it much, but if you if like the style of workflow it
enables, it might nice.

So, I haven't worked on pywm much, and can't at the moment, but I do
have plans concerning it. Among other things, I've considered rewriting
or adapting it to use the (hopefully) to be python interface to the new
x lib. But for now, do with it as you please. I'd be glad to hear from
big improvements though, and if you continue to develop it, it would
nice of you to tell about them on the webpage.

Elmo, the third (named) maintainer

(forwarding to the list also)