Am 01.06.2011 16:41, schrieb Thomas Adam:
On Wed, Jun 01, 2011 at 04:28:56PM +0200, Christian Ehrlicher wrote:
Hi,
I've a problem with xembed + qt (4.7,4.8) + fvwm2 (2.6.1). The attached
testcase works fine with kde.
How to reproduce:
- compile the two programs (qmake, make)
- start 'x11embedwidget'
- start 'x11embedcontainer<winId>' whith the winid provided by x11embedwidget
On KDE I now see a red window and when pressing a key both applications
receive this event (the widget will receive it twice - don't know if this is
correct but that's another problem).
It's correct.
On Fvwm2 I see a blue window and when I resize the window a small red area
appears. Key events are only visible on both applications when the mouse
cursor is in the blue area. In the red area the embedcontainer doesn't get
keyevents at all.
That's right again, because one is a child of the other internally.
It looks like fvwm doesn't move the child window to the new position
when it gets reparented. E.g. when I move the child to 0,0 (screen
coords) before reparenting, then reparent it to the new window, the
child still is at 0,0 (screen coords) and not 0,0 (parent coords). When
I do a XMoveResizeWindow to 0,0 afterwards, the child correctly moves to
0,0 (parent coords). This doesn't look like a Qt-only problem to me.
Now I only don't understand the problem with the key events. It looks
like the child is eating the keyevents or they're not given to the
parent. This works fine with KDE but I could not find anything inside
kwin sources which could explain this... any ideas?
btw: you don't make it easy to me to argue pro using fvwm2 in our
environment :(
Christian
