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

[Nils O. F. <ni...@no...>]

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 
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 
comfortable to work on.

When I start my pywm derivate (wm1.py), on a new Xnest with no applications, 
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=:22
$ ./wm1.py

However when one application is running inside Xnest before I start wm1.py it 
works.. (Started like this):
$ Xnest -ac -geometry 800x480 :22 &
$ export DISPLAY=:22
$ xclock&
$ ./wm1.py

So , is this another bug, or is it something  I dont do right..?

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 content 
for debugging of window-handling.

-- 
Mvh,
Nils Olav Fossum